Integration of a block chain, managing group authority and access in an enterprise environment

ABSTRACT

A block chain defining authority and access to confidential data may not be encrypted, and the access to the block chain can be regulated by the block chain itself and an access control server operating in an enterprise information technology (IT) environment. To incorporate authority defined in multiple sources, such as the block chain and the access control server, a token can be created containing multiple layers of permissions, i.e. constraints, coming from multiple sources. Each additional permission attenuates the authority granted by the token. When a processor controlling the access to the block chain receives the token, the processor can check the validity of the token and the authority granted by the token to determine whether the requester is authorized to access at least a portion of the block chain.

CROSS-REFERENCE TO RELATED APPLICATIONS

The present application is a divisional of U.S. patent application Ser.No. 17/156,316 filed on Jan. 22, 2021, which is a continuation of U.S.patent application Ser. No. 16/828,003 filed on Mar. 24, 2020, whichclaims priority to and benefit of U.S. Provisional Patent ApplicationNo. 62/830,002, filed Apr. 5, 2019, each of which is hereby incorporatedby this reference in its entirety.

TECHNICAL FIELD

The present application is related to managing access to a secured filesystem, and more specifically, to methods and systems that manage groupauthority and access to the secured file system in an enterpriseenvironment.

BACKGROUND

The major problem our computing systems face today is that internalthreats—that is, threats from our reliance upon a centralizedinfrastructure and the people that manage and provide it—are a part ofthe overall threat model. According to Microsoft SharePoint Admin Roledocumentation, “[g]lobal admins and SharePoint admins don't haveautomatic access to all sites and each user's OneDrive, but they cangive themselves access to any site or OneDrive.” Our current approach toinfrastructure, that centralizes the management and provision ofsecurity and access control with admins allows people access toinformation without a need-to-know that information. As a result,administrators that do not have the authority to read data stored on theserver that they are administering can still gain access and read thedata, without the authority to do so.

SUMMARY

Presented here is a system that manages a secure file system, and anauthority to access the file system, by granting access only to a userwho is authorized to access the file system. Access granted to the usercannot exceed the authority of the user. The user within the system isidentified using a cryptographic key unique to each user. The user'sauthority is recorded in a linear sequence, akin to a block chain, whichis distributed among multiple devices. Each of the multiple devicesindependently verifies the validity of each block in the linearsequence, thus preventing a compromised central server from grantingunauthorized access. The validity of the linear sequence is guaranteedby preventing certain operations from being performed on the linearsequence, such as branching of the linear sequence, deletion of theblocks within the linear sequence, and modification of the blocks withinthe linear sequence. Prior to adding a new block to the linear sequence,the validity of the block is independently computed by each of thedevices in the system to ensure that the user requesting the addition ofthe block has the authority to add the block to the linear sequence, andmore specifically, to perform the operation specified by the contents ofthe block.

The block chain itself may not be encrypted, and the access to the blockchain can be regulated by the block chain itself and an access controlserver operating in an enterprise information technology (IT)environment. To incorporate authority defined in multiple sources, suchas the block chain and the access control server, a token can be createdcontaining multiple layers of permissions, i.e. constraints, coming frommultiple sources. Each additional permission attenuates the authoritygranted by the token. When a processor controlling the access to theblock chain receives the token, the processor can check the validity ofthe token and the authority granted by the token to determine whetherthe requester is authorized to access at least a portion of the blockchain.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 shows a system to manage group authority and access tocryptographically secure data in a decentralized environment.

FIG. 2 shows a team linear sequence and a space linear sequence.

FIG. 3 shows the linear ordering between a team linear sequence and aspace linear sequence.

FIG. 4 shows anatomy of a block.

FIG. 5 shows verification of various layers of policies that can existwithin the system.

FIG. 6 shows various cryptographic IDs that can exist within the system.

FIG. 7 shows how a block can be distributed to multiple devices.

FIG. 8 shows a linear sequence containing blocks.

FIG. 9 shows a team linear sequence and a space linear sequence.

FIGS. 10A-B show authority computation in case a malicious actor triesto infiltrate the system.

FIGS. 11A-C show how access to encrypted data can be controlled uponauthority revocation.

FIG. 12 is a flowchart of a method to manage authority, via adistributed ledger, separately from access to encrypted data by one ormore trusted devices, wherein each of the trusted devices corresponds toat least one cryptographic key-based identity.

FIG. 13 is a flowchart of a method to manage access to encrypted datausing a distributed ledger.

FIG. 14 shows how the secure file system can be integrated into anenterprise information technology (IT) infrastructure, according to oneembodiment.

FIG. 15 shows how the secure file system can be integrated into anenterprise IT infrastructure, according to another embodiment.

FIG. 16A shows how a clock can be implemented using a block chain.

FIG. 16B shows contents of a clock block chain.

FIG. 17 shows a cryptographic tree.

FIG. 18 shows anatomy of a token.

FIG. 19 shows a token preventing a replay attack.

FIG. 20 shows how a recovery key can be used.

FIG. 21 shows a split key system limiting an attack to the encrypteddata when a user device is compromised.

FIG. 22 shows an update to the interpretation of the semantics of ablock chain.

FIG. 23 is a flowchart of a method to generate a token providingauthorization credentials.

FIG. 24 is a flowchart of a method to create an attenuated token.

FIG. 25 is a diagrammatic representation of a machine in the exampleform of a computer system 2500 within which a set of instructions, forcausing the machine to perform any one or more of the methodologies ormodules discussed herein, may be executed.

DETAILED DESCRIPTION Managing Group Authority and Access to Secure Datain a Decentralized Environment

FIG. 1 shows a system to manage group authority and access tocryptographically secure data in a decentralized environment. The server100 is in communication with multiple devices 110, 120, 130, 140, 150,also called endpoints. Each of the devices 110-150 can be associatedwith an entity or a user such as Alice, Bob, Carol, Dave, Ellen,respectively. Each user Alice-Ellen can have a unique cryptographic useridentification (“ID”), as explained later in this application, and eachdevice can have a unique cryptographic device ID. Each cryptographicuser ID can have one or more cryptographic device IDs associated withit.

The unique cryptographic user IDs can be separated into teams, such asteam 1 and team 2 as shown in FIG. 1. For example, Alice's, Bob's andCarol's cryptographic user IDs can be members of team 1, while Dave'sand Ellen's cryptographic user IDs can be members of team 2, as shown inFIG. 1. Team 1 and team 2 can have mutually exclusive membership, asshown in FIG. 1, or can have partially overlapping membership. The teammembership can be recorded in a linear sequence, for example, a teamlinear sequence 160, 170 (only one instance of a team linear sequencelabeled for brevity). Each team 1, 2 can have one team linear sequence160, 170, respectively. The linear sequence, such as the team linearsequence 160, 170 and a space linear sequence 190, 192, 194, is acryptographic data structure akin to a ledger. Because the linearsequence can be distributed across multiple devices, each of whichindependently verifies the linear sequence, the linear sequence canrepresent a distributed ledger.

Each team 1, 2 can have one or more spaces 180, 182, 184 (only oneinstance of a space labeled for brevity). Each space 180, 182, 184 canbe a virtual compartment containing encrypted data and members havingaccess to the encrypted data. A subset of team members can be includedin one or more spaces 180, 182, 184 and given authority to accessencrypted data associated with the one or more spaces 180, 182, 184. Forexample, team 1 has space 180, and all the team members Alice, Bob andCarol are invited to space 180. In another example, team 2 has space 182and 184. Space 182 only has Dave as a member, while space 184 has bothDave and Ellen as members. Each space 180, 182, 184 can have encrypteddata that can be made accessible only to the space members. Encrypteddata can include content or data, or both. For example, encrypted datacan include a file, a file system, a document, and/or messages such asinstant messages, emails, chat messages, text messages, etc.

In an example, only users Alice, Bob, Carol have authority to theencrypted data associated with space 180. In another example, only userDave has the authority to the encrypted data associated with the space182, while both users Dave and Ellen have the authority to accessencrypted data associated with space 184. Authority to the encrypteddata can include permission to read, write, and/or modify the encrypteddata. Access to encrypted data can be granted upon verifying that thecryptographic user ID requesting the access has the authorityencompassing the access.

For example, user Ellen's cryptographic user ID can have the authorityto read the encrypted data. However, if user Ellen's cryptographic userID requests to write to the encrypted data, user Ellen's cryptographicuser ID will be denied the access to write to the encrypted data becauseuser Ellen's cryptographic user ID lacks the authority. In other words,in the system disclosed here, the access to the encrypted data cannotexceed the authority associated with the encrypted data.

In another embodiment, the teams 1, 2 do not exist, and the users can begrouped into one or more spaces 180, 182, 184. To generate a space, ageneral pool of cryptographic user IDs that exist in the system can besearched to define the members of the space. The team linear sequence160, 170 can be integrated into the corresponding space linear sequence190, 192, 194 (only one instance of a space linear sequence labeled forbrevity). For example, the space linear sequence 190 can include theteam linear sequence 160 and the space linear sequence 192, the spacelinear sequence 192 can include the team linear sequence 170 and thespace linear sequence 192, while the space linear sequence 194 caninclude the team linear sequence 170 and the space or list 194.

A record of the authority associated with the encrypted data can becomputed by combining the team linear sequence 160, 170 and acorresponding space linear sequence 190, 192, 194, as described furtherin this application. In addition to storing authority and membership,the space linear sequence 190, 192, 194 can also store the encrypteddata and/or references to the encrypted data.

A copy of the team linear sequence 160, 170 and the space linearsequence 190, 192, 194 can be distributed to all the devices 110-160whose cryptographic user IDs are members of the corresponding team andspace as well as the server 100. For example, devices 110-130 have acopy of the team linear sequence 160 and the space linear sequence 190because the cryptographic user IDs associated with the devices 110-130are members of team 2 and space 180. In another example, device 140 hasa copy of the team linear sequence 170 and space linear sequences 192and 194, because user Dave's cryptographic user ID associated with thedevice 140 is a member of team 2 and space 182, 184. In a third example,device 150 has a copy of the team linear sequence 170 and space linearsequence 194, because user Ellen's cryptographic user ID associated withdevice 150 is a member of team 2 and space 184.

The metadata contained in the team linear sequence 160, 170 and thespace linear sequence 190, 192, 194 can be stored in plain text, whilethe remainder of the data can be encrypted. The metadata can includeauthority information, policy information, roles, etc., stored withinthe team linear sequence 160, 170 and the space linear sequence 190,192, 194. The remainder of the data can include confidential data suchas files, filesystems, messages, and/or other confidential data. Forexample, filenames can be a part of the confidential data if theencrypted data includes files and/or filesystems. The filesystems,files, and/or messages can only be accessed by knowing the encryptionkey used in encrypting the data. Even if an attacker were tosuccessfully gain control of the encryption key, a user's private key,and/or authorized endpoint device, the compromise of the system would belimited.

For example, if the attacker gains control of the encryption keyassociated with space 182, the attacker would only be able to accessconfidential data within the space 182, not the confidential data withinspaces 184 and 180. If an attacker obtains Ellen's private key, theattacker would only be able to access confidential data within the space184, and not spaces 180 and 182. Thus, by compartmentalizing authorityand access to spaces 180, 182, 184, the breach of the system can beconfined.

FIG. 2 shows a team linear sequence and a space linear sequence. A teamlinear sequence 200 can be used to track identities of team members andtheir authority in a team. A space linear sequence 210 can be used toform a secure compartment which can admit a subset of the team members.The secure compartments are used to manage data and negotiate sharedkeys among the space members. The team linear sequence 200 can beconnected to a program 220 containing a system policy, as well as to adatabase 230 containing facts. The space linear sequence 210 can rely onthe team linear sequence 200 to determine policy within the space. Thespace linear sequence 210 can be connected to a database 250 containingfacts.

The team linear sequence 200 and the space linear sequence 210 can eachcontain multiple blocks 205, 207, 209, 215 (only 4 labeled for brevity).The initial block 205 of the team linear sequence 200 can define apolicy for the team. A policy can specify a role and an authorityassociated with the role. For example, a policy can specify “onlyadministrators can create spaces within a team.” A team policy can beobtained from a policy template stored in a policy database and/or canbe modified when instantiating the first block 205. Alternatively, thefirst block 205 can define the team policy without reference to thepolicy template. A policy program 220 can be shared between differentteams. The different teams, however, can have different fact databases230. The team policy can also be modified by later blocks added to theteam linear sequences 200, if the team policy defining block 205 permitsmodification.

The policy program 220 can store policy templates that can be includedand/or modified as policy in the initial block 205. The fact database230 can contain unique key-value pairs that can define user and userauthority within the system. For example, a key-value pair that can beadded to the fact database 200 can be “Alice-administrator”, after ablock that specifies that Alice is an administrator has been verified.

Block 207 of the team linear sequence 200 can include a profile of theuser that is a member of the team 200. The user profile can include theuser's identity 240 which can be represented by a cryptographic user ID,such as a public-key in an asymmetric cryptographic algorithm such asRivest-Shamir-Adleman (RSA) or Diffie Hellman (DH). Only the user can bein possession of the private-key. The user profile can also include acryptographic device ID 242, 244 associated with all the devices thatthe user has approved.

There are multiple ways that a device can be added to the system. Forexample, the user can approve the device by sending a request to add thedevice to the system, where the request is signed with a private key ofthe user. In another example, to approve a device, the user can performa multi-step process. In the first step, the user can create a new setof device keys using the asymmetric cryptographic algorithm. In thesecond step, the user can sign the device keys with the user's privatekey and construct a device certificate containing the device public-keyand the user's private key signatures. In the third step, the device cansend a request, which includes the certificate from the second step, tobe added to the team, where the request is signed using the deviceprivate key. The system can authenticate that a team member has made therequest by verifying the request using the public-key of the user. Thecryptographic device ID can be a cryptographic hash of the public-key ofthe asymmetric cryptographic algorithm, while the private-key can beknown only to the device and can be used to authenticate actionsperformed by the device.

Block 209 of the team linear sequence 200 can include an event such asaddition of a new user, creation of the space linear sequences 210, achange to policy 205, removal of an existing user, and/or a change ofrole of a user.

Block 215 of the space linear sequence 210 can include an event such asaddition of a user to the space, addition of encrypted data to thespace, removal of a user from space, etc. Each event 215 in the spacelinear sequence 210 complies with the policy defined in the team linearsequence 200. In some embodiments, policy cannot be changed in the spacelinear sequence 210 and must be changed in the team linear sequence 200.A team can have multiple spaces with different policies by definingmultiple space types having different policies, and establishing thespaces corresponding to the different space types. For example, a spacetype can include an “administrator space type” where all users haveadministrator roles and administrators add and remove other users andcan have read and write access to the encrypted data. In anotherexample, the space type can include “stratified space type” where someusers have administrator roles, and some users have user roles, and theadministrator roles have more authority than the user roles. Events inthe team linear sequence 210 that change authority of a user can bestored in the fact database 250.

User policy 205 can be defined to enable users matching certainattributes to only have access to the space linear sequence 210 andspace encrypted data for a limited amount of time. The passage of timecan be measured by an always increasing clock that can provide atimestamp 260, 270, 280, 290 for each block 215 in the space linearsequence 210. The timestamp 260 can, for example, state “11:46 AMNovember 21, 2019 (PST).” In the space linear sequence 210, thetimestamp 260, 270, 280, 290 is always increasing between subsequentblocks. To enable time-limited access to the space linear sequence 210and associated encrypted data, the user policy 205 can state that “userassociated with profile 1 can have access to the linear sequence untilDecember 2, 2019.”

FIG. 3 shows the linear ordering between a team linear sequence and aspace linear sequence. Because the policy at least partially definingauthority is stored in the team linear sequence 310, to compute anauthority in a space linear sequence 300, a reference to the team linearsequence 310 needs to be made.

For example, in block 320 of the space linear sequence 300, the user ofthe space requests to add another user. In block 330 of the team linearsequence 310, the policy defined authority of the space user to addanother space user, however in block 340 of the team linear sequence310, the policy was modified to prevent space users from adding othersspace users. To determine whether block 320 is valid and should be addedto the space linear sequence 300, the linear sequence of blocks 330, 340in the team linear sequence 310 and the blocks 320, 350, 360 in thespace linear sequence 300 needs to be established.

To establish the linear sequence, a temporal relationship 370, 380, 390can be established between the blocks 320, 350, 360 in the space linearsequence 300 and the blocks 330, 340 in the team linear sequence 310.The temporal relationship 370, 380, 390 can include a pointer from thespace block 320, 350, 360 to the team block which is the immediatepredecessor or immediate successor of the space block 320, 350, 360. InFIG. 3, the temporal relationships 370, 380, 390 point from the spaceblock 320, 350, 360 to the immediately preceding team block. Forexample, temporal relationship 370, 380 indicates that the team block330 is the immediate predecessor of space blocks 320, 350, meaning thatspace blocks 320, 350 were created after the team block 330, but beforeteam block 340. Similarly, the temporal relationship 290 indicates thatspace block 360 was created after team block 340.

FIG. 4 shows anatomy of a block. The block 400, 410, can contain one ormore events 1-6. The events 1-6 in blocks 400, 410 can be atomic. Eachevent 1-6 is committed in a single block 400, 410.

A transaction can include one or more events where the last event issigned. A transaction can be produced by a single client, such as client110 in FIG. 1. When a transaction includes multiple events, such astransaction 1 containing events 1 and 2, the events can be ordered bythe client prior to being sent to the server. The ordering of the eventsis indicated using arrows 420, 430, 440, 450. Upon receivingtransactions 1-4 from multiple clients, the server can ordertransactions according to the order indicated by the arrows 420, 430,440, 450.

Events in a single transaction point to each other, and the last eventis signed. For example, events 1 and 2 form a single transaction 1.Similarly, events 5 and 6 form a single transaction 4. The arrow 420between event 3 and event 2, indicates that a server should commit event3 to the linear sequence after event 1. Similarly, the arrow 430 betweenevents 5 and 6 indicates that the server should commit the event 6 tothe linear sequence after event 5.

In an embodiment, events 1 and 2 come from a single client, while event3 can come from the same client as events 1 and 2, or from a differentclient. Similarly, events 5 and 6 come from a single client, while event4 can come from the same client or a different client. Further to thisembodiment, there can be at least one and up to four clients creatingtransactions 1-4, as shown in FIG. 4. For example, a single client canauthor transaction 1, including events 1 and 2. A second client canauthor transaction 2 including event 3. A third client can authortransaction 3 including event 4, and a fourth client can authortransaction 4 including events 5 and 6.

In the case that more than one event, for example, events 1-3, need tobe added in an atomic manner, the events 1-3 can be combined into asingle block 400, and the block 400 can be stored in the linearsequence. In the block 400, 410, only the last event, such as event 3,6, respectively, can be signed and none of the events 1-3, 4-6 in theblock 400, 410 are valid unless they all appear in the intended order inthe intended block.

The events 1-6 in blocks 400, 410 are cryptographically signed andrecorded in an authenticated linear sequence, as explained in thisapplication. The structure of the linear sequences guarantees thatdevices 110-160 in FIG. 1, which accept a block with some index n, arecertain to agree on the contents of all blocks with an index less thann. Blocks 400, 410 have indices 1, 2, respectively, in FIG. 4.

Once the block 400, 410 is finalized, the block 400, 410 gains a blockID. Finalizing a block means committing a block to a durable storage andnot changing the block. A block ID is a tuple of the block's index, andthe cryptographic hash of its contents. For a given block n, all eventsintended to be added to the linear sequence in block n+1 can includeblock ID of block n. This ensures that the intended ordering of eventsof devices 110-160 is preserved. Additionally, only devices which agreeon the block order and contents of blocks 0 through n, can accept anevent in block n+1.

FIG. 5 shows verification of various layers of policies that can existwithin the system. An events 500 is processed using a formal policywhich may either reject an event 500 or accept an event 500, andoptionally update a database of facts 510, 520. A fact database 510, 520is an index over the linear sequence with respect to the policy. Theindex is a collection of key value pairs. For example, the fact database510, 520 can record facts generated by the event 500 and the policy rulewhich authorized it. The fact database 510, 520 can be read by a policypressor when deciding if the event 500 is valid and should be acceptedin the linear sequence, such as a team linear sequence, or a spacelinear sequence.

When a server 100 in FIG. 1 receives the event 500, the server caninclude the event 500 in the next block. When the device 110-160receives the event 500, the device can process the event 500 based onthe business needs.

The system policy 530 is implemented by the device 110-160 and server100. All cooperating devices 110-160 must use the same system policy 530when processing the same block. In one embodiment, system policy 530 canbe implemented as source code in a programming language such as Rust,Python, Go, or a proprietary policy language. The system policy 530describes the structure of the blocks themselves. The system policy 530describes the core protocol of the linear sequences, such as “all eventsin block n must reference block n−1.”

The user policy 540 can be the team policy 205 in FIG. 2. The teampolicy 205 can be provided by a customer and can be tailored to thecustomer's organization. To ensure that all parties agree on the userpolicy 540, the user policy 540 can be stored in the linear sequence,such as the team linear sequence 310 in FIG. 3, and is guaranteed to bethe same for all users cooperating on a particular linear sequence. Anexample of a team policy rule is “only team admins can add new membersto a team.”

The application policy 550 can be defined per team 160, 170 in FIG. 1.The key difference between the application policy and other policies isthat the application policy operates after any cyphertext has beendecrypted. Consequently, the application policy cannot be checked by theserver. The application policy may not record authority, and can specifylow level rules such as “two files cannot have the same name.” Theapplication policy 550 can encode rules to resolve low-level conflictssuch as “if two files have the same name, the second file is ignored.”Policies, including the system policy 530, the user policy 540 and/orthe application policy 550, can be fixed in the program or managed usingthe linear sequences, such as team linear sequence 200 and space linearsequence 210 in FIG. 2.

FIG. 6 shows various cryptographic IDs that can exist within the system.Identities form the foundation of the security. Identities arerepresented by cryptographic identification (ID), such as asymmetric keypairs generated off-line using RSA, DH or other asymmetric algorithms.The public-key from the asymmetric key pair is used as the cryptographicidentity of the entity, while the private-key from the asymmetric keypair is known only to the entity. The off-line generation of the rootasymmetric key pairs protects the key pair from being compromised by abad actor. Device keys can be generated online but may be stored in ahardware security module (HSM).

A cryptographic ID, such as a cryptographic device ID or cryptographicuser ID, represents a single entity in the system, such as a device or auser, respectively. Consequently, the identity established using thecryptographic ID is globally distinct. In an embodiment, users areunique across teams even if no administrators distinguish them. Evenbetween non-cooperating groups, such as teams that do not share anymembers, the identity established using the cryptographic ID remainsglobally distinct.

The cryptographic user IDs can be used to sign/authorize device keyswhich are used operationally in the system. Devices can usecryptographic device IDs, which can include three keys types:administrative signing keys, message signing keys, and device encryptionkey. All of these key types are asymmetric key pairs and can be managedoutside of the application, in an operating system (OS) keys store or ahardware security module (HSM).

The identity certificate 600 can be deterministically generated from arecovery secret, allowing efficient hand transcription of the recoverysecret when provisioning a new device.

The administrative signing key 610 can be used in high-risk operationsand can require proof of user presence for any signing request. Examplesof the high-risk operations are adding users or changing permissions.

The message signing key 620 can be used to sign most data transmitted bythe device 110-160 in FIG. 1 and does not require proof of presence. Anexample use of the message signing key 620 is to sign messages sent in achat, or to sign files to be uploaded.

The device encryption key 630 can be used when sending a confidentialmessage to the device is necessary. The device encryption key 630 can berotated often to provide for forward secrecy for device to devicecommunications.

FIG. 7 shows how a block can be distributed to multiple devices. Devices700, 710, 720 can belong to the same space and/or team. They all canhave a copy of the linear sequence 730. When one of the devices, such asdevice 700, adds a new block 740 to the linear sequence 700, the device700 sends the new block 740 to the server 750.

The server 750 also has a copy of the linear sequence 730. The server750 can compute whether the block 740 is valid by computing whether theuser has the authority to perform the operation represented in the block740. To determine whether the user has the authority, the server 750 cancompute the authority from the linear sequence 730. The authoritycomputation is explained below.

Once the server 750 verifies that the block is valid, the server candistribute the block 740 to the devices 710, 720, which in turn can alsocompute whether the block 740 is valid based on the authority recordedin the linear sequence 730. If the device 710, 720 determines that theblock is not valid, the device can shut down because likely a breach ofthe system has occurred.

The devices 700, 710, 720 can share encrypted data 760, if they are inthe same space. The encrypted data 760 is encrypted using at least onecryptographic key, such as a confidential session key, explained below.Different devices 700, 710, 720 can have different authority to theencrypted data 760 such as read-only, write-only, and read and writeauthority.

The server 750 can also store the encrypted confidential data 760,however the server 750 does not store any of the cryptographic keys,including the confidential session key. The server 750 does not have anyauthority to the encrypted data 760. The server 750 has a copy of theencrypted data 750 to ensure availability of the data. For example, ifthe devices 700, 710 are off-line, and the device 720, as a newly addedmember of the space, requests the encrypted confidential data 760, theserver 750 can provide the encrypted confidential data 760 to the device720, even if the devices 700, 710 are off-line.

FIG. 8 shows a linear sequence containing blocks. The linear sequence800 contains at least blocks 810, 820, 830. Block 810 contains multipleevents 812, 814, while block 820 contains events 822, 824. Block 810 isthe initial block in the linear sequence 800 and contains the policy 816defining authority for the linear sequence 800. Each event in thesubsequent blocks, such as block 820, can be verified to ensure that theevent 822, 824 is consistent with the policy 816.

Each block subsequent to the initial block, such as block 820, includesthe cryptographic hash 826 of the previous block, which for block 820would be the hash of block 810. By including the cryptographic hash ofthe previous block, the ordering of the blocks in the linear sequence800 can be guaranteed, and a reordering or editing of existing blocks,and/or an insertion of new blocks within the linear sequence 800 can bedetected and automatically rejected.

The linear sequence 800 does not require a proof of work to verify thevalidity of the block, because the linear sequence 800 is a linearsequence, without any branching. Further, when a block is added to thelist, the block's validity has been checked to comply with the policyand authority recorded in the linear sequence 800, and the block cannotbe deleted. In other words, the order list 800 cannot be rolled back.

Within the initial block 810, event 812 establishes Alice as the user.The event is signed by Alice, meaning that Alice uses her private-key toencrypt the statement “Alice is a user.” To verify that Alice is trulyrequesting to be established as a user, a processor can verify thesigned statement “Alice is a user,” using Alice's public-key and ifverification succeeded the processor can know that Alice has trulyrequested to establish the user.

Event 814 establishes Alice as an administrator. Similarly, the event issigned and the processor can verify Alice's identity, as explainedabove. Because block 810 is the initial block, the policy 816 for thelinear sequence is established. For example, policy 816 can state “onlyadministrators can add users.” Once block 810 has been committed to thelinear sequence 800, the effective roles of the system are that Alice isan administrator and Alice is a user.

Event 822 in block 820 establishes that Bob is a user. To computewhether Alice has the authority to add the user, the processor can checkthe policy 816 and Alice's role in the system established by events 812,814. Because the policy specifies that only administrators can addusers, the processor checks whether Alice is an administrator. Uponverifying that Alice is an administrator, the processor can verify thatAlice has the authority to add Bob as a user. Each event subsequent tothe events contained in the initial block 812, 814, can be checkedagainst the policy 816, and the policy authorizing the event can berecorded. For example, for event 822, block 820 can point to the policystating that “only administrators can add users,” and a processor cancheck that there is a fact stored in a fact database that “Alice is anadministrator.”

Event 824 adds Carol as a user and must also be signed by Alice, asexplained above. Event 822 can also point to the policy that authorizedthe event, namely the policy stating “only administrators can add users”which is supported by the fact that “Alice is an administrator.” Thehash 826 creates a linear sequence of blocks 810, 820. After block 820has been committed to the linear sequence 800, the effective roles inthe system are that Alice is an administrator, and Alice, Bob, and Carolare users.

Other roles can be defined within the team such as legal, technical,sales etc. Each role can be granted access to a corresponding spacetype. For example, if Alice has role of “legal,” Alice can be grantedaccess to all spaces that have type “legal.” If Alice's “legal” role isrevoked, Alice can automatically lose access to the spaces that havetype “legal.”

FIG. 9 shows a team linear sequence and a space linear sequence. In thisexample, the team linear sequence 900 and the block linear sequencecontain blocks that include only one event. The team linear sequence 900is initialized with the initial block 910 and using connection 915linked to the policy 920, which establishes the policy for the team andany spaces. In block 930, Alice adds Bob as a user, and this event canbe linked, using connection 935, to the policy 920 that authorizes it.

In block 940, Bob creates space “planning,” and the event is linked tothe policy 920 to ensure that Bob as the user has the authority tocreate a space. By default, only the creator of the space is grantedadministrative authority to the space on the space linear sequence 970.If policy 920 authorizes users to create spaces, the block 930 isvalidated, the event is linked using connection 945 to the policy 920,and the block 940 is added to the team linear sequence 900. When Bobcreates space “planning,” space linear sequence 970 is established, withthe initial block 980 pointing to block 940 to indicate that the listwas created after block 940, but before block 950, explained below.

In block 950, Alice limits space creation to administrators. This actionchanges the policy 920. To verify whether block 950 is valid, aprocessor needs to check the policy 920 to see if the policy allowsadministrators to modify the policy. If the policy 920 allowsadministrators to modify the policy, the event is linked, usingconnection 955, to a portion of policy 920 that allows administrators tomodify the policy, and the new policy 925 is established. Even thoughafter block 950, Bob cannot create a space, because Bob had theauthority in block 942 to create the space, the space that Bob createdis valid. In block 960, Alice adds Carol, and the event is checkedagainst the new policy 925. Once the event is approved as authorized bythe new policy 925, the connection 965 is established to that portion ofthe new policy 925 that authorizes the event.

In block 990 of the space linear sequence 970, Bob adds Carol as a user.To verify whether block 990 is valid, the processor needs to check thenew policy 925 to see if policy 925 allows space users to add otherspace users. The policy 925 allows users to add users, and the event islinked, using connection 995, to a portion of the policy 925 thatauthorizes the event.

As explained earlier, only team members can be added to the space. IfBob attempts to add Carol prior to the block 950, the processor wouldnot authorize the addition of the block 990, because after checking thefact base and/or the team linear sequence 900, the processor candetermine that Carol is not a member of the team. However, if Bobattempts to add Carol to the space linear sequence 970 after block 960,the processor will authorize the addition of block 990, because thepolicy allows space users to add space users, and because Carol is amember of the team.

FIGS. 10A-B show authority computation in case a malicious actor triesto infiltrate the system. This example illustrates how a compromise ofthe server 1000 does not compromise the devices 1010, 1020, 1030 becauseeach device 1010-1030 independently checks and guarantees a validity ofthe linear sequence 1040 and the authority recorded in the linearsequence 1040.

If the server 1000 is compromised, for example, by a malicious serveradministrator who coerces the server 1000 into incorrectly verifying anddistributing a fraudulent block 1050 to the devices 1010-1030, eachdevice 1010-1030 can independently verify the validity of the block1050.

In FIG. 10B, each device 1010-1030 can independently verify that thehash 1060 of the last block in the linear sequence 1040 is valid. Eachdevice 1010-1030 can verify that user is a valid role. Each device1010-1030 can verify that Mal's signature is valid because, prior tosubmitting block 1050, Mal has requested that the server 1000 generate apublic-key and a private-key for him and distribute the public-keys tothe devices 1010-1030. However, the device 1010-1030 can determine thatblock 1050 is not valid because, according to system policy, onlyexisting members, such as administrators or users, can add new users,and Mal is not an administrator or a user. Because the block 1050 doesnot satisfy policy, all the devices 1010-1030 can reject the block 1050.In addition, the devices 1010-1030 can shut down once an invalidtransaction is received from the server 1000, because the devices1010-1030 can conclude that the server 1000 has been compromised.

FIG. 11A-C show how access to encrypted data can be controlled uponauthority revocation. Devices 1100, 1110, 1120 can share encrypted data1130, by, for example, being part of the same space. The encrypted data1130 can be encrypted using an Advanced Encryption Standard (AES), asymmetric-key algorithm using the same key for both encrypting anddecrypting the data. The encrypted confidential data 1130 can be storedon the devices 1100-1120 and the server 1140. The AES key can be knownonly to the devices 1100-1120 that have the authority to access theencrypted data 1130.

Assuming Alice is an administrator and has the authority to removeusers, Alice can submit a block 1150 to the server, that states “Carolis not a user,” thus revoking Carol's authority to any future encrypteddata shared between Alice and Bob. The server 1140 can distribute theblock 1150 to all the devices 1110-1120, as seen in FIG. 11B.

Upon validation of the block 1150, by the devices 1110-1120, Carol andher device 1120 lose the authority to access any future encrypted data.To ensure that Carol and her device 1120 cannot access any futureencrypted data shared between Alice and Bob, devices 1100, 1110 generatea new channel session key.

The new channel session key can be generated using the cryptographicmethods such as elliptic curve cryptography, for example, using a P-384elliptic curve. The channel session key can be generated using secretkey generation materials 1170, such as domain parameters in the case ofelliptic curve cryptography. The domain parameters can include theconstants A, B defining the elliptic curve Y²=X³+AX+B.

The new group of devices that share the key is computed based on thelinear sequence 1160. The secret key generation material 1170 isencrypted using each of the public-keys of an asymmetric cryptographicalgorithm belonging to the devices remaining in the new group ofdevices. The encrypted secret key generation materials 1170 aredistributed to all the devices in the group. The devices 1100, 1110 canuse their own private-keys of the asymmetric cryptographic algorithm todecrypt the received encrypted message. As a result, only devices 1100,1110 having the private key corresponding to the public-key used inencryption can calculate the new channel session key.

Devices 1100, 1110 receiving the secret key generation materials 1170can compute a private portion 1172 of the channel session key and apublic portion 1174 of the channel session key, and can record thepublic portion 1174 of the channel session key to the linear sequence1160. As a result of committing the public portion 1174 of the channelsession key to the linear sequence 1160, a client having an access tothe linear sequence 1160 can access the public portion 1174 and havewrite-only access to the linear sequence 1160. The client cannot readany of the encrypted data associated with the linear sequence 1160,because the client does not have the secret key generation materials1170 and/or the private portion 1172 of the channel session key. Theprivate portion 1172 of the channel session key is not recorded in thelinear sequence 1160.

Because the linear sequence 1160 does not require proof of work, andduplicating the linear sequence 1160 can be computationally feasible, acompromised server 1140 can present two different linear sequences 1162,1164 to two groups of users, as seen in FIG. 11C. For example, thecompromised server 1140 can refuse to distribute block 1150 to device1120, thus leading the device 1120 to believe it is still in the groupand to attempt to share encrypted data 1190 of device 1120 with devices1100 and 1110. Consequently, a new channel session key 1180 can becomputed based on the hash of the last block 1150 in the linear sequence1160. For example, the new channel session key 1180 can be obtained byperforming HKDF(channel session key in FIG. 11B, hash of block 1150). Asa result, since devices 1100 and 1110 do not share the same last blockwith the device 1120, device 1120 cannot compute the same channelsession key 1180.

In addition to the users of the same space Alice and Bob, a guest usercan be temporarily granted access to the encrypted data contained in thesame space as Alice and Bob. The guest user does not have access to theteam linear sequence 1160 and cannot validate authority of a user withinthe space linear sequence 1160. However, the guest user can stillnegotiate a channel session key with Alice and Bob and be granted atemporary access to the encrypted data 1130.

FIG. 12 is a flowchart of a method to manage, via a distributed ledger,authority separately from access to encrypted data by one or moretrusted devices, wherein each of the trusted devices corresponds to atleast one cryptographic key-based identity. In step 1200, a processorcan create a block defining an authority of a user. The block caninclude a cryptographic user ID uniquely identifying the user and anauthority associated with the cryptographic user ID. The authority candefine at least an operation associated with the cryptographic user IDto perform on the encrypted data. The operation can include read-only,write-only, or read and write. Unlike a bitcoin ledger which requiresapproval to work, the block does not require an entry approving work,thus generation of the block is less processor intensive compared tobitcoin, which, on average, requires 10 minutes of processor time togenerate a proof of work for the block.

In step 1210, the processor can append the block to an end of a linearsequence, including multiple blocks defining an authority associatedwith the encrypted data, and preserves a membership and an ordering ofeach block in the multiple blocks. To preserve the membership of theblock, no block in the linear sequence can be deleted. In other words,deletion is not allowed operation on the linear sequence. To preserveordering of each block among multiple blocks, rollbacks are not anallowed operation of the linear sequence. In other words, the linearsequence cannot branch, and contents of a block in the linear sequencecannot be modified and/or edited once the block is added to the linearsequence. The prohibition of deletion and modification of blocks ensuresintegrity of the linear sequence. In other words, once a block is addedto the linear sequence, the block is permanently in the linear sequence.Further, before a block is added to the linear sequence, the contents ofthe block must be verified to ensure they are consistent with thepreceding blocks in the linear sequence.

In step 1220, the processor can receive a request to access theencrypted data. The request can include a cryptographic user IDassociated with the user making the request. Access to the encrypteddata can include read-only, write-only, or both read and write access.

In step 1230, the processor can determine whether the user making therequest has an authority to access the encrypted data by computing theauthority recorded in the linear sequence as shown in FIGS. 8, 9, and10A-B. To compute the authority, the processor can check the linearsequence from an initial block to a last block to determine user rolesand authority associated with each role, and to compare the request fromthe user to the user role. In other words, the processor can manageaccess to the encrypted data by the cryptographic user ID by checkingthat the access by the cryptographic user ID is permitted by theauthority recorded in the linear sequence.

In step 1240, the processor can grant access to the encrypted data tothe user making the request upon determining that the user making therequest has the authority to access the encrypted data.

The processor can create an initial block in the linear sequencedefining a policy specifying a role and an authority associated with therole. For example, the initial block 810 in FIG. 8 defines policy 816 inFIG. 8. Further, the processor can create the block in the linearsequence defining a role associated with the cryptographic user ID. Theblock can be the initial block 810, as shown in FIG. 8 which, inaddition to defining policy, defines that Alice is an administrator inevent 814 in FIG. 8, or the block can be a subsequent block, such asblock 820 in FIG. 8, which defines Bob and Carol as users.

To preserve the ordering of each block in the multiple blocks, theprocessor can include a cryptographic hash (“hash”) of each previousblock in each subsequent block, thus enabling detection of any change inthe ordering sequence, as explained in FIG. 8. For example, theprocessor can compute a second cryptographic hash of data contained in asecond block in the multiple blocks. The second block can be the initialblock, or any block, in the linear sequence. The processor can store thesecond cryptographic hash within the second block, and can include thesecond cryptographic hash in data contained in a block subsequent to thesecond block.

To preserve the membership of blocks within the linear sequence, theprocessor can define a set of operations to be performed on the linearsequence, where any operation outside of the defined set cannot beperformed in the linear sequence. The defined set can exclude operationssuch as deletion, branching of the linear sequence, and/or modificationof data within the linear sequence.

To reduce the likelihood of a failure, such as corrupting the linearsequence and/or the encrypted data by a compromised central server, theprocessor can distribute the linear sequence to multiple devices. Eachdevice in the multiple devices can be cryptographically verified by acryptographic user ID associated with the linear sequence, as explainedin FIG. 2. For example, to add a device to the list of authorizeddevices, an already authorized cryptographic user ID needs to requestaccess for the device, as explained in FIG. 2. Upon receiving therequest, the processor can verify that the cryptographic user ID indeedmade the request by decrypting the request using the public-key of thecryptographic user ID. Upon verification, the processor can assign acryptographic device ID to the device.

Each device among the multiple devices having the cryptographic deviceID can independently verify the validity of a request based on theauthority computed based on the linear sequence, as explained in FIGS.10A-B. If a device cannot verify that the block is valid based on thecomputed authority, the device can refuse to add the block. Upon failureto verify, the device can shut down to prevent tampering with theencrypted data on the device.

The processor can define a team of cryptographic user IDs, forefficiency purposes, so that not all the cryptographic IDs have to besearched to find a group of people who can share encrypted data amongstthemselves. To create the team, the processor can create a team linearsequence including multiple blocks. The multiple blocks can include oneor more policy blocks, one or more profile blocks, and one or moreauthority blocks. The one or more policy blocks can define a policyestablishing a role and an authority associated with the role, the oneor more profile blocks can establish a cryptographic user ID and acryptographic device ID associated with the cryptographic user ID, andthe one or more authority blocks can define the role associated with thecryptographic user ID. The team linear sequence is an instance of, andhas the same properties as, the linear sequence described in thisapplication.

The policy recorded in the initial block of a linear sequence, such asthe team linear sequence, can be modified if the policy recorded in theinitial block permits modification. If the policy recorded in theinitial block does not permit modification, any block attempting tomodify the policy will not be verified by the multiple devices.

To modify the policy, the processor can obtain a request to modify thepolicy defined in the one or more policy blocks and a cryptographic IDof a user making the request. The processor can check whether thecryptographic user ID is authorized to modify the policy by determiningauthority associated with the cryptographic ID from the team linearsequence. Usually only administrators are allowed to modify the policy,and the processor can check whether the cryptographic user ID has a roleof an administrator or a user. If the cryptographic user ID has the roleof a user, the processor can refuse to verify the block. Upondetermining that the cryptographic user ID is authorized, the processorcan create a policy block specifying the modification and can append thepolicy block defining the modification to the end of the team linearsequence.

Once the processor defines the team, the processor can define a spacewithin the team, which has a subset of the team members that canprivately share encrypted data. The space membership can be the same asthe team membership or can be smaller than the team membership. Thespace is a virtual compartment defining encrypted data and access to theencrypted data. The space can include the encrypted data using acryptographic key known only to the members of the space.

To define the space the processor can represent the members and theencrypted data by creating a space linear sequence. For efficiency, thespace linear sequence can be subdivided into multiple linear sequences.For example, the space linear sequence can be subdivided into anauthority linear sequence, and the encrypted data linear sequence. Theauthority linear sequence can define a role within the space of thecryptographic user ID. The cryptographic user ID is a member of thespace and the role is consistent with the policy defined in the one ormore policy blocks of the team. The encrypted data linear sequence canrecord operations performed on the encrypted data such as addition,deletion or modification of at least a portion of the encrypted data.

The encrypted data can include multiple types of encrypted data such asfiles, emails, messages, etc. The processor can create a linear sequencefor each of the encrypted data types. So, instead of creating oneencrypted data linear sequence, the processor can create a linearsequence for the files, a linear sequence for the emails and a linearsequence for the messages.

By creating a separate linear sequences for authority and for each typeof encrypted data, the processor can speed up the computation ofauthority because to compute the authority, the processor need onlyexamine the linear sequence of blocks containing data pertaining toauthority, as opposed to examining linear sequence containing authorityblocks as well as encrypted data blocks. Assuming that there are as manyauthority blocks as encrypted data blocks, by splitting up the spacelinear list into the authority linear list and encrypted data linearlist, the processor can speed up the computation of authority by afactor of two. Similarly, the processor can speed up retrieval ofencrypted data by approximately a factor of 2, because to retrieve theencrypted data, the processor need only examine the encrypted datalinear sequence, as opposed to linear sequence containing both encrypteddata blocks and the authority blocks.

The processor can revoke membership of a cryptographic user IDassociated with the space. When membership is revoked, the cryptographicuser ID must be prevented from accessing and encrypted data sharedwithin the space after the revocation of cryptographic user IDsmembership. To prevent the cryptographic user ID from accessingencrypted data added to the space after the revocation, the processorcan generate a cryptographic session key unknown to the cryptographicuser ID whose membership has been revoked, and can encrypt the encrypteddata added to the space after the revocation using the cryptographicsession key. The data contained in space prior to the revocation canalso be encrypted using the new cryptographic session key.

The new cryptographic session key can be an AES key computed using thefollowing 4 steps. In step 1, the AES key can be computed using ellipticcurve algorithm such as P-384. In step 2, the remaining group of devicesis computed from the space linear sequence, for example, the authoritylinear sequence within the space. In step 3, the AES key is encryptedusing a public device key of each device still in the space, and theencrypted AES key is distributed to each device within the space. Eachdevice can decrypt encrypted AES key because each device knows its ownprivate device key. Since no other devices know the private-key of thedevice, no eavesdroppers can decrypt the encrypted AES key. In step 4, amessage encrypted using the AES key can be distributed to the deviceswithin the space to ensure that everybody can decrypt the message.

In some instances, such as described in FIG. 11 C, the computation ofthe session key can include an additional step performed before step 3,in which the computation of the session key also includes acryptographic hash of the last block in the space linear sequence, suchas the authority linear sequence of the space. Specifically, once theAES key is computed in step 1, to generate the final key an additionalstep of combining the AES key and the cryptographic hash of the lastblock can be performed. The combination can be computed using the HKDFcryptographic function which takes his arguments the AES key and thecryptographic hash of the last block to produce the final key. The finalkey is then encrypted and distributed to all the devices.

In addition to computing the new session key once a member is removedfrom the list, the new session key can be computed when a new member isadded, and the intent is to prevent the member from accessing theencrypted data shared within the space prior to the member joining.

The processor can enable a linear ordering of the team linear sequencein the space linear sequence by establishing a temporal relationshipbetween multiple team blocks belonging to the team linear sequence andmultiple space blocks belonging to the space linear sequence, asexplained in FIG. 3. There can be various types of temporalrelationships, such as a space block can be bound to a team blockimmediately preceding the space block, or the space block can be boundto a team block immediately succeeding the space block, etc.Establishing the linear order is important in authority computation aswell as auditing.

For example, to determine the authority, reference needs to be made tothe current policy defined in the team space at a time prior to theaddition of the block. In another example, when performing auditing ofthe linear sequences, to determine whether a block was correctly addedto a space linear sequence, the current authority needs to be computedwhich can be partially defined on the team linear sequence. To determinethe current policy, a linear order of the blocks within the space linearsequence and the team linear sequence needs to be determined, so thatthe authority recorded in the team list prior to addition of a block canbe computed.

Consequently, every time a block is added to the space linear sequence,the block is bound to the team linear sequence to determine the linearorder between the team linear sequence and the space linear sequence.The linear order between two space linear sequences does not need to beestablished because the authority within the one space linear sequencedoes not affect the authority within the other space linear sequence.

FIG. 13 is a flowchart of a method to manage access to encrypted datausing a distributed ledger. In step 1300, a processor can manage accessto the encrypted data by checking that the access is permitted by anauthority recorded in a linear sequence including multiple blocksarranged, where an initial block in the linear sequence defines a policyspecifying a role and an authority associated with the role.

In step 1310, the processor can preserve a validity of the authorityrecorded in the linear sequence by cryptographically identifying a userassociated with the linear sequence, thus preventing an authorized userfrom accessing the linear sequence. Prior to adding a block associatedwith a user authority to the multiple blocks, the processor can checkthe linear sequence to ensure the user authority is consistent with thepolicy. Upon ensuring that the user authority is consistent with thepolicy, the processor can add the block associated with the userauthority to the multiple blocks.

The processor can determine a user role associated with the user, anauthority associated with the user role and can ensure the userauthority associated with the block is within the limits of theauthority associated with the user role.

For example, a block to be added to the sequence can request amodification of the policy. Prior to adding the block to the sequence,the processor can check whether the policy permits verification, andwhat role can modify the policy. For example, the policy can state thatthe policy can be modified but that only an administrator can modify thepolicy. If that is the case, the processor can check whether the userrequesting modification is an administrator or not.

To prevent unauthorized access to the data by a compromised centralserver, the processor can distribute a linear sequence to multipledevices associated with multiple users, wherein each device in themultiple devices is cryptographically authenticated by a user in themultiple users. The determination whether to add a block to the linearsequence can be made independently by each of the devices, instead ofbeing made by the central server, which creates a single point offailure.

The processor can authenticate each user using a cryptographic user ID,which can be a public-key generated using an asymmetric cryptographicalgorithm. The cryptographic user ID can be a string of 2,048 bits. Theasymmetric cryptographic algorithm can be RSA or DH, and can generatetwo keys, a public-key and a private-key. The processor can provide afirst key (i.e., the private-key) in the asymmetric cryptographic keypair only to the user, and the cryptographic user ID (i.e., thepublic-key) in the asymmetric cryptographic key pair to multiple usersinto the whole system. The processor can use the public-key is a way toidentify the user throughout the system. As a result, the user canassume different names in different teams or spaces, and the variousnames can be tied to one cryptographic user ID.

For example, to verify the user's identity, the processor can receive atext message and the text message can be signed using a private-key ofthe user. To verify the user's identity, the processor can use theuser's public-key (i.e., the cryptographic user ID) to reverse thesigning process. The processor can then compare the text message and themessage obtained by reversing the signing process. If the text messageand the message obtained by reversing the signing process are an exactmatch, the processor can verify the user's identity. Otherwise, theprocessor cannot verify the user's identity.

For efficiency purposes, the processor can create a team. To create ateam the processor can obtain multiple cryptographic user IDsidentifying multiple users. The processor can create the linear sequenceincluding the multiple blocks arranged in the linear sequence, where theinitial block in the linear sequence defines the policy specifying therole and the authority associated with the role, and where a block inthe multiple blocks defines a role associated with a cryptographic userID in the multiple cryptographic user IDs identifying a user in themultiple users.

To create a space within the team, the processor does not have to searchall the cryptographic IDs in the system and can only search thecryptographic IDs contained in the team, thus preserving CPU cycles. Forexample, if a team contains 10 users, the whole system contains tens ofthousands of users, the number of processor cycles used to create thespace is reduced by approximately 1,000. The space can contain a subsetof the cryptographic user IDs of the team. The space can include thedata encrypted using a cryptographic key known only to the members ofthe space. The space can include a space linear sequence representingthe members and the encrypted data.

As explained in this application, the space linear sequence can containtwo or more sub-sequences for efficiency reasons. The space linearsequence can include an authority linear sequence containing blocksmodifying the authority within the system, such as adding or removingusers and/or administrators. Encrypted data linear sequence can includethe linear sequence adding, deleting, and modifying encrypted datawithin the system. Encrypted data linear sequence can be furthersubdivided into multiple linear sequences depending on the type of theencrypted data, such as files and/or messages.

The team linear sequence, the space linear sequences, and the encrypteddata can be stored in a memory configured to be continuously availableto one or more computers over a network, such as the central server. So,in case most of the devices within the space are off-line, a device inthe space can request encrypted data and/or can add a block to the spaceordered sequence from the central server.

Integration of a Block Chain Managing Group Authority and Access in anEnterprise Environment

FIG. 14 shows how the secure file system can be integrated into anenterprise information technology (IT) infrastructure, according to oneembodiment. The server 1400 can store encrypted data 1410, which caninclude confidential data such as the file system, emails, instantmessages, etc. The server 1400 can also store the block chains 1402,1404, 1406, 1408, 1412 which can represent a team linear sequence or aspace linear sequence, as described in this application. A block chainis a growing list of records, called blocks, that are linked usingcryptography. Each block contains a cryptographic hash of the previousblock, for example, 826 in FIG. 8, and data, for example, 812, 814, 816,822, 824 in FIG. 8. A block can also include a timestamp, for example,260, 270, 280, 290 in FIG. 2.

The block chains 1402, 1404, 1406, 1408, 1412 can record authorityassociated with a cryptographic user ID, as explained in thisapplication. The block chains 1402, 1404, 1406, 1408, 1412 can be storedin plain text, and the server 1400 can control access to the blockchains 1402, 1404, 1406, 1408, 1412 by allowing access to the plain textonly to authorized requesters. To authorize a requester, the server 1400can issue and manage tokens, as explained below.

The system 1420 can be implemented on customer premises, as part of anenterprise IT infrastructure. The system 1420 can include an accesscontrol server 1430, a token issuer 1440 and a user device 1450.

The access control server 1430 can control the user device's 1450 accessto web applications, services and/or files running on the enterpriseinfrastructure by granting or denying permission to the user device 1450based on a set of enterprise policies. The access control server 1430can run various software such as, Microsoft Active Directory, or AppleOpen Directory.

The token issuer 1440 can act as middleware between the access controlserver 1430, the user device 1450 and the server 1400. The token issuer1440 can receive a token request 1460 from the user device 1450requesting access to a portion of the block chain 1402, 1404, 1406,1408, 1412. The token request 1460 can include a cryptographic user IDassociated with the user making the request, and a specification of theportion of the block chain 1402, 1404, 1406, 1408, 1412 being requested.For example, the token request 1460 can include the cryptographic userID in the form of an alphanumeric string, such as“9EDaleMN9CUy1V7VSYyAUTkfEGC7MUDMkugmXV VsM7Z5r01Wpg,” and anidentification of a team block chain 1402, 1408 or a space block chain1404, 1406, 1412.

The token issuer 1440 can send a request 1470 for a token from theserver 1400 granting permission to the user device 1450 to access thespecified portion of the block chain. The token request 1470 can includethe cryptographic user ID and the identification of the team block chain1402, 1408 or the space block chain 1404, 1406, 1412 contained in thetoken request 1460.

Upon receiving the token request 1470, the server 1400 can computewhether the cryptographic user ID has the authority to access therequested portion of the block chain 1402, 1404, 1406, 1408, 1412 basedon the membership information stored in the block chain 1402, 1404,1406, 1408, 1412. For example, if the cryptographic user ID requestsaccess to space block chain 1404, the server 1400 can check whether thecryptographic user ID is a member of the space block chain 1404. If thecryptographic user ID is a member of the space, the server 1400 candetermine that the cryptographic user ID has the necessary authority andcan issue a token 1480. Otherwise, the server 1400 can determine thecryptographic user ID is not authorized to access the space block chain1404 and can refuse to issue the token 1480.

The token 1480 can grant unlimited read access to the requested portionof the block chain, such as the space block chain 1404. In other words,whenever the server 1400 and/or the token issuer 1440 receive the token1480 from any source, the server 1400 does not perform the authoritycomputation described above, and immediately grants access to theportion of the block chain specified in the token 1480, such as thespace block chain 1404. Effectively, the token 1480 creates anefficiency gain by allowing the server 1400 to not perform the expensivecomputation of calculating authority every time the cryptographic userID requests access to the space block chain 1404. Instead, the token1480 allows the server 1400 to perform a less expensive calculation ofsimply verifying the token 1480, as described below.

Before passing the token 1480 to the user device 1450, the token issuer1440 can check with the enterprise access control server 1430 for whatkind of permissions the user device 1450 has regarding the space blockchain 1404. To perform the check, the user device 1450 can send a ticketrequest 1490 to the access control server 1430. The ticket request 1490can contain the access control server user identification, such as theuser's login ID and the user's password. The user's login ID and theuser's password used to identify the user to the access control server1430 are different from the cryptographic user ID used to identify theuser to the server 1400.

Upon verifying the user's identification, such as the login ID and thepassword, the access control server 1430 can check a permission that theuser has according to the company policy and send the ticket 1492,including the permission, to the token issuer 1440. For example, thecompany policy can specify that while the user is on vacation, the userdoes not have access to email. Consequently, the permission can specifyvarious restrictions such as “the user is allowed access only when theuser is at a particular location, such as inside the company building,”“the user is allowed access only during a particular time,” and/or “theuser is only allowed access when the user device 1450 is connected to aparticular network,” such as the company network.

The token issuer 1440 can incorporate the permissions specified in theticket 1492 into the token 1480 to obtain an attenuated token. Thepermissions specified in the ticket 1492 may not increase thepermissions granted by the token 1480 but can either leave thepermissions unchanged or attenuate, that is, reduce, the permissionsgranted by the token 1480.

In addition, the token issuer 1440 can add additional restrictions to anattenuated token, such as when the attenuated token expires (e.g.,within 3 or 5 minutes), location restrictions, Internet addressrestrictions, etc. The additional restrictions can be added to theattenuated token to produce the attenuated token 1494, which is sent tothe user device 1450.

The user device 1450 can request to be added to a team block chain 1402,1408. To be added to the team, the user device 1450 can authenticateitself with the access control server 1430, which can send the ticket1492 authenticating the user, to the token issuer 1440. In addition, thetoken issuer 1440 can authenticate the user with the server 1400 byasking the server to compute the authority stored in the team blockchain 1402, 1408 for the cryptographic user ID associated with the user.If both the access control server 1430 and the server 1400 authorize theuser, the user can be added to the team block chain 1402, 1408.

Even if the access control server 1430 is controlled by an adversary,because the access control server 1430 cannot increase the permissionsgranted by the token 1480, the adversary would still only have theauthority that is in the block chain 1402, 1404, 1406, 1408, 1412 andgranted by the token 1480. If the adversary controls the token issuer1440, the adversary can only control tokens 1480 for the teams that thetoken issuer 1440 has received from the server. In both cases, theadversary would only be able to read the plain text data, and not theencrypted data 1410. Further, the adversary would not be able to modifythe plain text data.

The token issuer 1440 can receive an indication of how much the accesscontrol server 1430 is trusted. If the access control server 1430 is nottrusted, the token 1494 can be issued or a user can be added to a team1, 2 without involving the access control server 1430.

FIG. 15 shows how the secure file system can be integrated into anenterprise IT infrastructure, according to another embodiment. Theaccess to the block chain 1502, 1504, 1506, 1512 can be managed withoutthe access control server 1430 in FIG. 14. The company policyimplemented by the access control server 1430 can be recorded on a blockchain 1520, or can be part of a fact database 1530. The block chain 1520and the fact database 1530 can exist independently of a team 1, 2 or aspace 1, 2. The server 1500 and the token issuer 1540 can be part of theenterprise IT infrastructure, and/or can be provided as a cloud service.Removing the access control server 1430 reduces a number of potentialsecurity issues and allows the system to function even if the accesscontrol server 1430 is not trusted.

When a user device 1550 requests a token using the token request 1560,the token issuer can forward the token request 1560 to the server 1500.The token request 1560 can contain the cryptographic user ID and anidentification of a portion of the block chain 1502, 1504, 1506, 1508,1512 to which the access is being requested. For example, theidentification of the portion of the block chain can identify the teamblock chain 1508.

The server 1500 can compute the authority of the cryptographic user IDrecorded in the team block chain 1508, to determine whether thecryptographic user ID is a member of the team. If the cryptographic userID is not a member of the team, the server 1500 can refuse to send atoken to the token issuer 1540. If the cryptographic user ID is a memberof the team, the server 1500 can check the facts database 1530 and/orthe company policy block chain 1520 to determine whether the companypolicy puts any restrictions on the access of the cryptographic user ID.In this case, a single cryptographic user ID can be used to check boththe permissions associated with the server 1500 and permissionsassociated with the company policy, as opposed to requiring separateauthentication, as explained in FIG. 14.

The server 1500 can send a message 1580 to the token issuer 1540. Themessage 1580 can include a token granting unrestricted read access tothe team block chain 1508, and permissions associated with the companypolicy. The token issuer 1540 can create the attenuated token 1594 bycombining the token and the permissions associated with the companypolicy and forward the attenuated token 1594 to the user device 1550.

The user device 1550 may want to further attenuate the attenuated token1594 to grant a permission to a third party to access the team blockchain 1508. To do so, the user device 1550 can send a request to thetoken issuer 1540 containing the attenuated token 1594 and theadditional permission imposed on the attenuated token, for example atemporal permission. The token issuer 1540 can incorporate theadditional permission into the attenuated token 1594, and issue a newtoken to send to the user device 1550, which the user device 1550 canforward to the third party.

Clock

FIG. 16A shows how a clock can be implemented using a block chain. Toincorporate the temporal permission, discussed in FIG. 15, a processorcan create an always increasing clock, as explained for example in FIG.2, where each block 1635, 1645 (only two labeled for brevity) in theblock chain 1610, 1615, 1620, 1625 is time stamped, such that optionaltimestamps 1630, 1640 within the blocks 1635, 1645 are alwaysincreasing.

The temporal permission in a token can be expressed in terms of thetimestamps, such as, the token is valid 5 minutes after the timestamp1630. So, if the timestamp 1640 is more than 5 minutes after thetimestamp 1630, a token holder is not allowed read access to the block1645. The blocks 1635, 1645 can be ordered within the team and thesequence but may not be able to be ordered between two different teamsor two different sequences. The timestamps 1630, 1640 can be placedwithin the header of the block 1635, 1645, respectively.

Instead, or in addition, the clock can be implemented using the blockchain 1600. The clock block chain 1600 can include blocks 1650, 1660,1670, etc., each representing a tick of the clock, such as 1 second, 1minute, 5 minutes, half an hour, an hour. The frequency of the blocks1650, 1660, 1670 can be related to the computational resources of theenterprise. The higher the computational resources, the more frequentthe block 1650, 1660, 1670, and the lower the computational resourcesthe less frequent the blocks 1650, 1660, 1670.

Each block 1625, 1635, 1645 (only three labeled for brevity) in teamblock chain 1610, 1615 can have a binding 1628, 1638, 1648,respectively, to a corresponding block 1650, 1660, 1670 in the clockblock chain 1600. For example, the team block 1625 has a binding 1628 tothe block 1650, meaning that the team block 1625 was created after thecreation of the block 1650, and before the creation of the block 1660.

The blocks 1680, 1690 (only two labeled for brevity) in the space blockchains 1620, 1625 can have a binding 1682, 1692, respectively, to acorresponding block 1635, 1625 to the team block chains 1610, 1615. Forexample, the binding 1682 indicates that the block 1680 is created afterthe block 1635, but before the block 1645.

Consequently, each block 1680, 1690 in the space block chains 1620, 1625is bound to the corresponding block in the team block chains 1610, 1615,and indirectly to the block 1650, 1660, 1670 in the clock block chain1600. For example, based on the bindings shown in FIG. 16A, block 1690is created after block 1650, but before block 1660.

The temporal permission in a token can be expressed in terms of theclock block chain 1600, block 1650, 1660, 1670, or in terms of a wallclock. The clock block chain 1600 can correspond to the wall clock, withthe constraint that the blocks 1650, 1660, 1670 in the clock block chain1600 are always increasing.

For example, when the temporal permission is formulated in terms of thewall clock, the temporal permission can state that the token is validuntil Dec. 1, 2020. The first block 1650, 1660, 1670 that has atimestamp after the specified date designates the time at which, andafter which, the token is no longer valid. All the blocks bound to thefirst block designating such time are not accessible to the tokenholder.

In another example, when the temporal permission is formulated in termsof the block 1650, 1660, 1670, the temporal permission can state thatthe token is valid for 1½ hours after block 1650. The first block 1660,1670 that has a timestamp after the specified time designates the timeat which, and after which, the token is no longer valid. All the blocksbound to the first block designating such time are not accessible to thetoken holder.

FIG. 16B shows contents of a clock block chain. The block 1650, 1660,1670 of the clock block chain 1600 can contain several fields includinga wall clock field 1652, 1662, 1672, sequence clock field 1654, 1664,1674 and a root of cryptographic hash tree field 1656, 1666, 1676.

The wall clock field 1652, 1662, 1672 can be a record of the timeindicated by a clock of a server storing the clock block chain 1600. Thewall clock fields 1652, 1662, 1672 do not have to be always increasing,so the fields 1652, 1662 can have the same value, or the field 1672 canindicate a time before the time indicated by field 1652.

The sequence clock 1654, 1664, 1674 is always increasing. The sequenceclock can be indicated by multiple servers that are measuring andagreeing on the current time. The multiple servers provide redundancy,so that if one server fails, the clock block chain 1600 can continuemeasuring time. The current time agreed upon has the property of beinggreater than the previous current time. The current time can be thelatest time measured by the multiple servers, or it can be a time thatthe most servers agree on, as long as the current time is greater thanthe previously agreed-upon current time.

The root of cryptographic hash tree field 1656, 1666, 1676 can be aMerkle root, and can include the cryptographic hash of all the mostrecent blocks in the block chains bound to the block 1650, 1660, 1670.For example, the cryptographic hash tree field 1662 can contain thecryptographic hash of block 1635 and block 1685. The reason to provide aroot of the cryptographic hash tree, instead of a list of all the mostrecent blocks, can be to preserve bandwidth and storage resourcesbecause communicating and storing the root is less expensive thancommunicating and storing the list of all the blocks. Another reason canbe to keep the list of all the blocks secret, by only providing the rootfrom which, with some additional information, the list of all the blockscan be calculated.

FIG. 17 shows a cryptographic tree. The endpoints represent block 1700,1710, 1720, 1730 that are all of the most recent blocks in the blockchains bound to a block in the clock block chain 1600 in FIG. 16. Thecryptographic tree 1740 is constructed by, at each node, computing acryptographic hash such as SHA of the child nodes. For example, node1750 is computed by computing the cryptographic hash of block 1710,while the node 1792 is computed by computing the cryptographic hash ofnodes 1770, 1780. Finally, the root 1790 is computed by computing thecryptographic hash of the nodes 1792, 1794.

The root 1790 can be stored in the clock block chain 1600. The value ofthe root 1790 is unique to the sequence of blocks 1700, 1710, 1720, 1730that generated the cryptographic tree 1740. Storing a single value, suchas root 1790, in the clock block chain 1600 preserves bandwidth andstorage space compared to storing the value of all the blocks 1700,1710, 1720, 1730. Further, storing the root 1790 does not disclose allthe blocks 1700, 1710, 1720, 1730 used in constructing the cryptographictree 1740.

To check whether a block is part of the cryptographic tree 1740, only asubset of all the elements in the cryptographic tree 1740 needs to besupplied. For example, if there are N endpoints, that is, N blocks usedin constructing the cryptographic tree 1740, only log (N) elements needto be supplied to check whether the root 1790 contains a particularelement.

In a more specific example, to check whether block 1710 is a member ofroot 1790, only the block 1710 and nodes 1760, 1792 need to be supplied.Once supplied, the value of the node 1750 can be computed from the valueof block 1710. The value of the node 1794 can be computed from the valueof the nodes 1750 and 1760, but, for example, by computing SHA(node1760, node 1750). The root node can be computed from the values of nodes1794 and 1792. If the so computed root node matches the root 1790 storedin the clock block chain 1600, the membership of the block 1710 in thecryptographic tree 1740 can be confirmed.

Token

FIG. 18 shows the anatomy of a token. The token 1800 can be the token1480 in FIG. 14, 1580 in FIG. 15, granted by a first authority source,such as the server 1400 in FIG. 14, 1500 in FIG. 15 storing theauthority-defining block chains 1402, 1404, 1406, 1408, 1412 in FIG. 14,1502, 1504, 1506, 1508, 1512 in FIG. 15.

The token 1800 can include a key identifier (ID) 1810 identifying asecret root key, a permission 1820 and a cryptographic hash 1830 of thepermission 1820 and the secret root key. The secret root key can beknown to the server 1400, 1500 and/or to the token issuer 1440 in FIG.14, 1540 in FIG. 15. Using the key identifier 1810, the server 1400,1500 and/or the token issuer 1440, 1540 can retrieve the secret rootkey. The cryptographic hash 1830 can be HMAC, sometimes expanded aseither a keyed-hash message authentication code or a hash-based messageauthentication code. HMAC can be used to simultaneously verify both thedata integrity and the authenticity of a message, as with any MAC. Anycryptographic hash function, such as SHA-256 or SHA-3, may be used inthe calculation of an HMAC. As with all cryptographic hashes, thecryptographic hash 1830 is not reversible, meaning given the output ofthe cryptographic hash 1830, determining the inputs into thecryptographic hash is not computationally feasible.

The token 1800, with an addition of a second permission 1850, can changeto become an attenuated token 1840. The attenuated token 1840 can be thetoken 1494 in FIG. 14, 1594 in FIG. 15. The second permission 1850 canbe granted by a second authority source such as the access controlserver 1430 in FIG. 14 or the company policy recorded in the block chain1520 in FIG. 15. The token 1800 can contain any number of permissions,which are also called constraints or caveats.

To obtain an attenuated token 1840, the server 1400, 1500 can add thesecond permission 1850 to the token 1840, compute a second cryptographichash 1860 of the first cryptographic hash 1830 and the second permission1850 and remove the first cryptographic hash 1830 from the token,thereby obtaining the attenuated token 1840.

The second permission 1850 is interpreted to only decrease the firstpermission 1820. By removing the cryptographic hash 1830 from the firsttoken, token 1840 is created where the first permission 1820 is limitedby the second permission 1850. Because the cryptographic hash 1860 isnot reversible, an attacker cannot guess the cryptographic hash 1830,and the token 1840 is secure. Consequently, the largest authority isgranted by the original token 1800, having only one permission 1820.

For example, the first permission 1820 can specify the cryptographicuser ID is being granted access to read metadata associated with blockchains 1402, 1404, 1408, 1412, 1502, 1504, 1508, 1512. The secondpermission 1850 can specify a team block chain, such as team block chain1402, 1408, 1502, 1508, to which the cryptographic user ID has access.Additional permissions can be added to the attenuated token 1840 to makean even more attenuated token 1870.

In one embodiment, the attenuated token 1870 can be generated uponrequest by a user device. For example, a third permission 1880 canspecify a space block chain 1404, 1406, 1412, 1504, 1506, 1512 withinthe team block chain 1402, 1408, 1502, 1508 to which the cryptographicuser ID can have access. A third cryptographic hash 1890 can be includedin the attenuated token 1870, or the cryptographic hash 1890 can be acryptographic hash of the cryptographic hash 1860 and the thirdpermission 1880. The cryptographic hash 1860 can be removed from thetoken 1870.

In another embodiment, the user device can grant the attenuated token1870 to a third party. For example, the third party can have aproprietary video processing algorithm, and the attenuated token 1870can grant access to a video that the user device has access to. Thereason for granting the access to the third party can be that a thirdparty has access to a faster network connection than the user device.The attenuated token 1870 can contain a third permission 1880 specifyingthe video to which the attenuated token 1870 grants access.

To request the video, the third party can send the attenuated token 1870to the server 1400, 1500 and/or to the token issuer 1440, 1540. Theserver can verify the token, as explained below, using the secret rootkey, and can grant access to the video to the third party.

FIG. 19 shows a token preventing a replay attack. To prevent an attackerfrom performing a replay attack by obtaining the token, and providing acopy of the token to the token issuer 1440 in FIG. 14, 1540 in FIG. 15,and/or the server 1400 in FIG. 14, 1500 in FIG. 15, the attenuatedtokens 1840, 1870 in FIG. 18 can include a single use permission 1900,1910 to obtain attenuated tokens 1940, 1970. The cryptographic hash 1920can be a cryptographic hash of the cryptographic hash 1860 in FIG. 18and the third permission 1900, while the cryptographic hash 1930 can bea cryptographic hash of the cryptographic hash 1890 in FIG. 18 and thefourth permission 1910. If the tokens 1940, 1970 are intercepted onrequest, replaying the token 1940, 1970 does not grant any access to theattacker because the tokens 1940, 1970 are not valid after the onerequest is satisfied.

Recovery Key

FIG. 20 shows how a recovery key can be used. Block chain 2000 cancontain block 2010. Block 2010 can be the initial block of the blockchain 2000, or it can be any other block in the block chain 2000. Block2010 can contain multiple events 2012, 2014, 2016. Most of the events inthe block chain 2000, like events 2012 and 2014, are signed by a publickey of a user entering the event, such as Alice. However, an event, suchas the event 2016, can be signed by a recovery key 2050.

The recovery key 2050 is a special key that circumvents entire authorityand policy computation. Before a processor even determines whether thepolicy authorizes the event 2016, the processor can determine whetherthe event is signed by the recovery key 2050. If the event is signedwith the recovery key 2050, the processor determines that the event isallowed regardless of authority and policy. Thus, the recovery key 2050overrides the entire authority and policy.

The recovery key 2050 needs to be protected extremely well.Consequently, the recovery key 2050 can be split into multiple parts2052, 2054, 2056 (only three labeled for brevity), such as 30 parts. Thedifferent parts 2052, 2054, 2056 can be put in different safe places,such as different HSMs, each having different operating procedures. Thedifferent parts 2052, 2054, 2056 can be encrypted, and one person canhave a password to store the key parts 2052, 2054, 2056 in a file, and adifferent person can have a password to retrieve the key parts 2052,2054, 2056 from the file. The assembly of the recovery key 2050 canrequire the participation of all, or at least a majority of, devices andusers having parts of the 2052, 2054, 2056 of the recovery key 2050,thereby safeguarding accidental use of the recovery key 2050.

The existence and the use of the recovery key 2050 can be optional. Therecovery key can be set to a predetermined value, such as all zeros,which indicates to the processor that the recovery key 2050 has not beengenerated and does not exist. The processor can ignore any event signedby the recovery key 2050 set to the predetermined value.

Split Key

FIG. 21 shows a split key system limiting an attack to the encrypteddata when a user device is compromised. The user device 2100 can storedata 2110 encrypted using multiple keys, such as a channel session key2120, as described in this application, as well as a split key 2130. Thesplit key 2130 can be separated into at least two parts 2132, 2134. Thefirst key part 2132 can be stored on the server 2140, while the secondkey part 2134 can be stored on the user device 2100.

To encrypt data, the user device 2100 can request the first key part2132 from the server 2140. Upon receiving the first key part 2132, theuser device 2100 can calculate a key derivation function (KDF) that is acombination of the first key part 2132 and the second key part 2134 toobtain the split key 2130 with which to encrypt the data. Similarly, todecrypt the encrypted data 2110, the user device 2100 can request thefirst key part 2132 from the server 2140 and calculate the split key2130 using the KDF, which is a combination of the first key part 2132and the second key part 2134.

Once the user device 2100 calculates the split key 2130, the user device2100 can forget the first key part 2132 based on a predetermined rule.The predetermined rule can state that for every time the user device2100 is suspended and/or rebooted, the first key part 2132 is forgotten;for every three files that are opened using the split key 2130, thefirst key part 2132 is forgotten; for every time the applicationassociated with the key derivation function is closed, the first keypart 2132 is forgotten; for every time a geolocation and/or an IPaddress of the user device 2100 is outside of a predefined space, thefirst key part 2132 is forgotten; etc.

Because the user device 2100 forgets the first key part 2132 based onthe predetermined rule, the server 2140 can revoke access to the userdevice 2100. For example, if the server 2140 is notified that the userdevice 2100 has been compromised, such as by being stolen and/or hackedby an attacker, the server 2140 can record that the request for thefirst key part 2132 from the user device 2100 should be refused. Thenext time the user device 2100 requests the first key part 2132, theserver 2140 can refuse to provide the first key part 2132. Consequently,the encrypted data 2110 remains encrypted on the user device 2100 and isnot available to the attacker.

To increase security of the first key part 2132, the server 2140 canrequire a multifactor authentication before providing the first key part2132. For example, the server 2140 can require a second device 2150 toprovide an authentication to the server 2140. Once the server 2140receives the authentication from the second device 2150, the server 2140can provide the first key part 2132 to the user device 2100.

System Updates

FIG. 22 shows an update to the interpretation of the semantics of ablock chain. The block chain 2200 can contain blocks 2210, 2220, 2230,etc. Rules for interpreting the semantics of the block chain 2200 can becoded in the blocks 2210, 2220, 2230, and can be represented as a sourcecode in a programming language such as Rust, Python, Go, or aproprietary language. Updating interpretation of the semantics of theblock chain 2200 (including authority, policy, etc.) can happen in theblock chain 2200.

For example, the block 2210 can contain source code updating how tointerpret the blocks 2230, subsequent to the block 2210. By putting thesemantics in the block chain 2200, every instance of the system, spreadacross multiple clients and containing different block chains, canupdate the local rules for interpreting the semantics of the block chainwhen they receive the block 2210. So, blocks 2220 preceding the block2210 are interpreted according to a first set of rules, while the blocks2230 subsequent to the block 2210 are interpreted according to thesecond set of rules established by the block 2210.

For example, the rules for interpreting the semantics of the block chain2200 can govern how race conditions are resolved. Such rules can bespecified in system policy 530 in FIG. 5, user policy 540 in FIG. 5 orapplication policy 550 in FIG. 5. Consequently, the block 2210 canupdate system 530, user 540, and/or application 550 policy.

To prevent introducing a bug into the rules for interpreting thesemantics of the block chain 2200, the policy engine 530, 540, 550 canbe formally verified. Formal verification is the act of proving thecorrectness of the policy 530, 540, 550 with respect to a certain formalspecification or property, using formal methods of mathematics. Theformal verification can provide assurance that there are no bugs in thepolicy 530, 540, 550.

Flow Diagrams

FIG. 23 is a flowchart of a method to generate a token providingauthorization credentials. In step 2300, a processor can create a blockchain including multiple blocks by creating a block defining anauthority of the user in appending the block to the end of the blockchain. The block can include a cryptographic user ID identifying theuser and an authority associated with the cryptographic user ID. Theauthority can define at least an operation associated with thecryptographic user ID to perform on the block chain. For example, theoperation can include read access, write access, and/or read/writeaccess to the block chain and/or to an encrypted data associated withthe block chain. The block chain may not be encrypted.

In step 2310, the processor can receive a request from a requestingdevice to access the block chain. The request can include acryptographic user ID associated with the user making the request, wherethe cryptographic user ID can be authorized by the block chain toperform certain operations. The requesting device can be a user device.

In step 2320, the processor can determine whether the user making therequest has an authority to access the block chain by computing theauthority recorded in the block chain including checking the block chainfrom an initial block to a last block. Performing the authoritycomputation can be expensive.

In step 2330, the processor can generate a token granting access to theblock chain to the user making the request upon determining that theuser making the request has the authority to access the block chain. Thetoken can be a certificate that proves the processor has done theexpensive operation of, for example, computing the authority on theblock chain, or checking the user's password. So, the next time theprocessor receives the token, the processor does not have to perform theexpensive operation, and instead can check the token, which can be acheaper operation than, for example, computing the authority in theblock chain. In step 2340, the processor can send the token to therequesting device.

The token can include a message and an HMAC taking two arguments,namely, the message and a secret root key, as explained in thisapplication. For example, the message can be a permission identifyingthe user authorized to access the block chain.

In one embodiment, when the user wants to read the block chain, the usercan send a signed message providing the cryptographic user ID andidentifying a portion of the block chain, such as a team and/or a space,that the user wants to read. A processor having access to the blockchain can check the public key associated with the cryptographic userID, the signature and the fact database to confirm that thecryptographic user ID has the permission to access the requested teamand/or space. If the processor does not make the confirmation, theprocessor can deny access to the user. If the processor confirms thatthe user has authority to access the team and/or the space, theprocessor can create a token including the cryptographic user and anindication of the requested team and/or space. The token can grant aread permission to the cryptographic user ID.

To generate the token, the processor can create a key identifieridentifying a secret root key. The key identifier can be implemented asan index into a database associated with the server. The secret root keycan be further protected using public-key or secret-key encryption. Theprocessor can create a permission to the block chain granted by thetoken, such as the user ID or the team and/or the space ID. Further, theprocessor can create a cryptographic hash of the secret root key and thepermission. The cryptographic hash can be an HMAC. The processor can addthe key identifier, the permission and the cryptographic hash to thetoken. The token can give read permission to the team and/or the space.

To determine whether the user making the request has the authority toact as the block chain, the processor can determine whether the requestis signed with a recovery key without computing the authority recordedin the block chain. As explained in this application, the recovery keycan override the authority recorded in the block chain. The processorcan generate a second token granting unlimited access to the block chainto the user making the request upon determining that the request issigned with the recovery key.

To prevent attackers from gaining access to the recovery key, therecovery key can be separated into multiple parts, where each part isencrypted using a different secret encryption key, and each encryptedpart is distributed among multiple devices such as HSMs.

To prevent attackers from gaining access to the system by compromisingan endpoint, for example, a user device, the encrypted data can beadditionally encrypted with a split key. The split key can be separatedinto two parts, the first part that is stored on a server, and thesecond part that is stored on the user device. To decrypt encrypteddata, the user device has to request the first part of the split key,that is, the first cryptographic key, from the server. Upon receivingthe request for the first cryptographic key, the server can determinewhether the user device is permitted to receive the first cryptographickey.

For example, the user device can be reported as stolen and consequentlynot permitted to receive the first cryptographic key. The server canrefuse to send the first cryptographic key upon determining that theuser device is not permitted to receive the first cryptographic key. Ifthe user device receives the cryptographic key, the user device cancompute a key derivation function which is a combination of the firstand the second cryptographic keys, such as HMAC, to obtain a key whichcan be used in decrypting the encrypted data.

The software updates to the computation of authority and/or policystored in the block chain can be stored, themselves, in the block chain.The server can receive an update regarding an interpretation ofsemantics of the block chain. The server can ensure consistency of theinterpretation of the semantics of the block chain across multiple userdevices by storing the update within the block chain.

FIG. 24 is a flowchart of a method to create an attenuated token. Instep 2400, a processor can obtain a token granting an access to a blockchain. The access to the block chain can be permitted by a firstauthority source defined by the block chain. In other words, the firstauthority source can be the block chain recording authority and policy,itself. The token can include a key identifier identifying a secret rootkey, a first permission to access the block chain authorized by thefirst authority source and a first cryptographic hash of the secret rootkey and the permission. Access to the block chain can be granted basedon whether the requester has read access to the encrypted data, ormembership in the requested team and/or space.

The first permission can include a cryptographic user ID to whom thefirst permission is granted, and an identification of at least a portionof the block chain to which the cryptographic user ID has access, suchas the team or space. The first permission can include an operationpermitted to be performed by the cryptographic user ID, or the permittedoperation may not be included and can be assumed that operation isread-only.

In step 2410, the processor can receive a request to access the blockchain from a requesting device, with a second permission from a secondauthority source limiting access associated with the requesting device.The second authority source can be an access control server such as anactive directory. The access control server can be part of an enterpriseIT system.

The second permission can include a time limitation or a geolocationlimitation. For example, the second permission can specify a time windowwithin which the axis is permitted, or a geolocation within which accessis permitted. In a more specific example, if the user leaves thebuilding, access to the block chain can be revoked. The secondpermission can also include an Internet address limitation, for example,permitting access to the requesting device as long as the Internetprotocol (IP) address of the requesting device is within a specified IPaddress range.

In step 2420, the processor can attenuate the access granted by thetoken by adding the second permission from the enterprise to the token,computing a second cryptographic hash of the first cryptographic hashand the second permission, and removing the first cryptographic hashfrom the token, thereby obtaining an attenuated token. The firstpermission and the second permission obtained from the first authoritysource and the second authority source, respectively, can be translatedinto multiple permissions and entries in the token and the attenuatedtoken. In step 2430, the processor can send the attenuated token to therequesting device such as the user device.

To obtain the token, the processor can compute the authority stored inthe block chain. The block chain can include multiple blocks wherein ablock in the block chain defines an authority of a cryptographic userID. The authority can define at least an operation associated with thecryptographic user ID to perform on the block chain. To determinewhether the user making the request has an authority to access the blockchain, the processor can compute the authority recorded in the blockchain including checking the block chain from an initial block to a lastblock. The processor can generate the token granting access to the blockchain to the user making the request upon determining that the usermaking the request has the authority to access the block chain.

The processor can grant access to the block chain upon receiving a validtoken. The processor can receive a request to access a portion of theblock chain and the attenuated token. The processor can obtain thesecret root key using the key ID stored within the attenuated token. Theprocessor can calculate the cryptographic hash of the secret root keyand the first permission to obtain a third cryptographic hash. Theprocessor can calculate the cryptographic hash of the thirdcryptographic hash and the second permission to obtain a fourthcryptographic hash. The processor can determine whether the secondcryptographic hash included in the attenuated token matches the fourthcryptographic hash by comparing the second cryptographic hash includedin the attenuated token and the fourth cryptographic hash. Upondetermining that the second cryptographic hash included in theattenuated token and the fourth cryptographic hash match, the processorcan grant the request to access the portion of the block chain. If thesecond cryptographic hash and the fourth cryptographic hash do notmatch, the processor can refuse to grant the request because theattenuated token is not valid.

The attenuated token can be attenuated further by adding additionalpermissions, that is, constraints or caveats, to the attenuated token.For example, the attenuated token holder may want to delegate a portionof his access to the block chain to a third party. Consequently, theattenuated token holder can request a creation of an additionalattenuated token granting a portion of the access to the third party.For example, the token holder can specify specific blocks within theteam to which the third party can have access.

To create an even further attenuated token, the processor can receivethe attenuated token and a request for a third permission. In oneembodiment, the processor can determine whether the third permission isauthorized by the first permission and the second permission. Forexample, the first permission and the second permission may grant accessto team 1 user Alice, while the third permission can request access toteam 2. The processor can determine user Alice does not have access toteam 2 and can refuse to create the attenuated token. In anotherexample, upon determining that the third permission is authorized by thefirst permission and the second permission, the processor can create asecond attenuated token by computing the cryptographic hash of thesecond cryptographic hash and the third permission, deleting the secondcryptographic hash from the attenuated token, adding the thirdpermission to the attenuated token, and adding the third cryptographichash to the attenuated token, thereby creating the second attenuatedtoken.

In another embodiment, the processor does not determine the validity ofthe permissions, and instead only creates the attenuated token. Thevalidity of the permissions can be determined at the time when thevalidity of the token is determined. If the third permission requestsdata not granted by the first and second permissions, a null responsecan be provided to the requester.

The processor can grant the token based on a recovery key. The processorcan determine whether the user making the request for the token has anauthority to access the block chain by determining whether the requestis signed with the recovery key without computing the authority recordedin the block chain. The processor can generate a second token grantingunlimited access to the block chain to the user making the request upondetermining that the request is signed with the recovery key. Asdescribed in this application, the processor can break up the recoverykey into multiple parts, such as 30 parts, encrypt each part, distributethe encrypted key parts to multiple devices, and require participationof at least the majority of the devices to assemble the recovery keyfrom the multiple parts.

To guard against an attacker infiltrating the system by compromising theuser device, the processor can implement a split key, where the firstcryptographic key is stored on the server, and the second cryptographickey is stored in the user device. When the processor receives therequest for the first cryptographic key from the user device, theprocessor can determine whether the user device is permitted to receivethe first cryptographic key upon receiving the request. For example, ifthe user device is reported as stolen, the processor does not permit theuser device to receive the first cryptographic key stored on the server.If the user device receives the cryptographic key, the user device canperform a KDF which is a combination of the first and the secondcryptographic key, such as HMAC, to obtain a key which can be used indecrypting encrypted data.

The processor can receive an update regarding an interpretation ofsemantics of the block chain. The processor can ensure consistency ofthe interpretation of the semantics of the block chain across multipleuser devices by storing the update within the block chain.

To enforce time sensitive permissions, such as time sensitivepermissions stored in the token, the processor can create a clock blockchain including multiple blocks. Each block among the multiple blockscan include a timestamp greater than a timestamp of a preceding block.The processor can create a temporal relation between a block in theblock chain and a clock block in the clock block chain. For example, alink between the block and the clock block can indicate that the blockhas been created before the clock block, after the clock block, at thesame time as the clock block, within specified time after and/or beforethe clock block, etc.

The processor can receive the token including a time-limited permission,and a request to access a portion of the block chain. The processor candetermine whether the time-limited permission is authorized by the clockblock chain associated with the requested portion of the block chain.The processor can refuse the request to access the portion of the blockchain upon determining that the time-limited permission is notauthorized by the clock block chain. For example, the latest block inthe clock block chain can be past the time-limited permission, or therequested portion of block chain has been created outside of thetime-limited permission window, etc.

Computer

FIG. 25 is a diagrammatic representation of a machine in the exampleform of a computer system 2500 within which a set of instructions, forcausing the machine to perform any one or more of the methodologies ormodules discussed herein, may be executed.

In the example of FIG. 25, the computer system 2500 includes aprocessor, memory, non-volatile memory, and an interface device. Variouscommon components (e.g., cache memory) are omitted for illustrativesimplicity. The computer system 2500 is intended to illustrate ahardware device on which any of the components described in the exampleof FIGS. 1-24 (and any other components described in this specification)can be implemented. The computer system 2500 can be of any applicableknown or convenient type. The components of the computer system 2500 canbe coupled together via a bus or through some other known or convenientdevice.

The computer system 2500 can represent the server such as 100 in FIG. 1,750 in FIG. 7, 1000 and FIG. 10 A, 1140 in FIGS. 11 A-C, 1400 in FIG.14, 1500 in FIG. 15. The computer system 2500 can represent the devices,such as 110-116 FIG. 1, 700-720 in FIG. 7, 1010-1030 in FIG. 10 A,1100-1120 in FIGS. 11 A-11 C, 1440 in FIG. 14, 1540 in FIG. 15, 1450FIG. 15, 1550 in FIG. 15. The processor of the system 2500 can performthe various methods and instructions described in this application. Themain memory, nonvolatile memory, and/or the drive unit of the system2500 can store the instructions to be performed by the processor. Thedevices 1110-1160, 700-720, 1010-1030, 1100-1120, and the server 100,750, 1000, 1140, 1400, 1500, 1440, 1540 can communicate with each otherusing the network interface device of the system 2500. For example, thetoken 1480, 1494 in FIG. 14, 1580, 1594 in FIG. 15 can be communicatedvia the network interface of the system 2500.

This disclosure contemplates the computer system 2500 taking anysuitable physical form. As example and not by way of limitation,computer system 2500 may be an embedded computer system, asystem-on-chip (SOC), a single-board computer system (SBC) (such as, forexample, a computer-on-module (COM) or system-on-module (SOM)), adesktop computer system, a laptop or notebook computer system, aninteractive kiosk, a mainframe, a mesh of computer systems, a mobiletelephone, a personal digital assistant (PDA), a server, or acombination of two or more of these. Where appropriate, computer system2500 may include one or more computer systems 2500; be unitary ordistributed; span multiple locations; span multiple machines; or residein a cloud, which may include one or more cloud components in one ormore networks. Where appropriate, one or more computer systems 2500 mayperform without substantial spatial or temporal limitation one or moresteps of one or more methods described or illustrated herein. As anexample and not by way of limitation, one or more computer systems 2500may perform in real time or in batch mode one or more steps of one ormore methods described or illustrated herein. One or more computersystems 2500 may perform at different times or at different locationsone or more steps of one or more methods described or illustratedherein, where appropriate.

The processor may be, for example, a conventional microprocessor such asan Intel Pentium microprocessor or Motorola power PC microprocessor. Oneof skill in the relevant art will recognize that the terms“machine-readable (storage) medium” or “computer-readable (storage)medium” include any type of device that is accessible by the processor.

The memory is coupled to the processor by, for example, a bus. Thememory can include, by way of example but not limitation, random accessmemory (RAM), such as dynamic RAM (DRAM) and static RAM (SRAM). Thememory can be local, remote, or distributed.

The bus also couples the processor to the non-volatile memory and driveunit. The non-volatile memory is often a magnetic floppy or hard disk, amagnetic-optical disk, an optical disk, a read-only memory (ROM), suchas a CD-ROM, EPROM, or EEPROM, a magnetic or optical card, or anotherform of storage for large amounts of data. Some of this data is oftenwritten, by a direct memory access process, into memory during executionof software in the computer 2500. The non-volatile storage can be local,remote, or distributed. The non-volatile memory is optional becausesystems can be created with all applicable data available in memory. Atypical computer system will usually include at least a processor,memory, and a device (e.g., a bus) coupling the memory to the processor.

Software is typically stored in the non-volatile memory and/or the driveunit. Indeed, storing and entire large program in memory may not even bepossible. Nevertheless, it should be understood that for software torun, if necessary, it is moved to a computer readable locationappropriate for processing, and for illustrative purposes, that locationis referred to as the memory in this paper. Even when software is movedto the memory for execution, the processor will typically make use ofhardware registers to store values associated with the software, andlocal cache that, ideally, serves to speed up execution. As used herein,a software program is assumed to be stored at any known or convenientlocation (from non-volatile storage to hardware registers) when thesoftware program is referred to as “implemented in a computer-readablemedium.” A processor is considered to be “configured to execute aprogram” when at least one value associated with the program is storedin a register readable by the processor.

The bus also couples the processor to the network interface device. Theinterface can include one or more of a modem or network interface. Itwill be appreciated that a modem or network interface can be consideredto be part of the computer system 2500. The interface can include ananalog modem, isdn modem, cable modem, token ring interface, satellitetransmission interface (e.g. “direct PC”), or other interfaces forcoupling a computer system to other computer systems. The interface caninclude one or more input and/or output devices. The I/O devices caninclude, by way of example but not limitation, a keyboard, a mouse orother pointing device, disk drives, printers, a scanner, and other inputand/or output devices, including a display device. The display devicecan include, by way of example but not limitation, a cathode ray tube(CRT), liquid crystal display (LCD), or some other applicable known orconvenient display device. For simplicity, it is assumed thatcontrollers of any devices not depicted in the example of FIG. 25 residein the interface.

In operation, the computer system 2500 can be controlled by operatingsystem software that includes a file management system, such as a diskoperating system. One example of operating system software withassociated file management system software is the family of operatingsystems known as Windows® from Microsoft Corporation of Redmond, Wash.,and their associated file management systems. Another example ofoperating system software with its associated file management systemsoftware is the Linux™ operating system and its associated filemanagement system. The file management system is typically stored in thenon-volatile memory and/or drive unit and causes the processor toexecute the various acts required by the operating system to input andoutput data and to store data in the memory, including storing files onthe non-volatile memory and/or drive unit.

Some portions of the detailed description may be presented in terms ofalgorithms and symbolic representations of operations on data bitswithin a computer memory. These algorithmic descriptions andrepresentations are the means used by those skilled in the dataprocessing arts to most effectively convey the substance of their workto others skilled in the art. An algorithm is here, and generally,conceived to be a self-consistent sequence of operations leading to adesired result. The operations are those requiring physicalmanipulations of physical quantities. Usually, though not necessarily,these quantities take the form of electrical or magnetic signals capableof being stored, transferred, combined, compared, and otherwisemanipulated. It has proven convenient at times, principally for reasonsof common usage, to refer to these signals as bits, values, elements,symbols, characters, terms, numbers, or the like.

It should be borne in mind, however, that all of these and similar termsare to be associated with the appropriate physical quantities and aremerely convenient labels applied to these quantities. Unlessspecifically stated otherwise as apparent from the following discussion,it is appreciated that throughout the description, discussions utilizingterms such as “processing” or “computing” or “calculating” or“determining” or “displaying” or “generating” or the like, refer to theaction and processes of a computer system, or similar electroniccomputing device, that manipulates and transforms data represented asphysical (electronic) quantities within the computer system's registersand memories into other data similarly represented as physicalquantities within the computer system memories or registers or othersuch information storage, transmission or display devices.

The algorithms and displays presented herein are not inherently relatedto any particular computer or other apparatus. Various general purposesystems may be used with programs in accordance with the teachingsherein, or it may prove convenient to construct more specializedapparatus to perform the methods of some embodiments. The requiredstructure for a variety of these systems will appear from thedescription below. In addition, the techniques are not described withreference to any particular programming language, and variousembodiments may thus be implemented using a variety of programminglanguages.

In alternative embodiments, the machine operates as a standalone deviceor may be connected (e.g., networked) to other machines. In a networkeddeployment, the machine may operate in the capacity of a server or aclient machine in a client-server network environment, or as a peermachine in a peer-to-peer (or distributed) network environment.

The machine may be a server computer, a client computer, a personalcomputer (PC), a tablet PC, a laptop computer, a set-top box (STB), apersonal digital assistant (PDA), a cellular telephone, an iPhone, aBlackberry, a processor, a telephone, a web appliance, a network router,switch or bridge, or any machine capable of executing a set ofinstructions (sequential or otherwise) that specify actions to be takenby that machine.

While the machine-readable medium or machine-readable storage medium isshown in an exemplary embodiment to be a single medium, the term“machine-readable medium” and “machine-readable storage medium” shouldbe taken to include a single medium or multiple media (e.g., acentralized or distributed database, and/or associated caches andservers) that store the one or more sets of instructions. The term“machine-readable medium” and “machine-readable storage medium” shallalso be taken to include any medium that is capable of storing, encodingor carrying a set of instructions for execution by the machine and thatcause the machine to perform any one or more of the methodologies ormodules of the presently disclosed technique and innovation.

In general, the routines executed to implement the embodiments of thedisclosure, may be implemented as part of an operating system or aspecific application, component, program, object, module or sequence ofinstructions referred to as “computer programs.” The computer programstypically comprise one or more instructions set at various times invarious memory and storage devices in a computer, and that, when readand executed by one or more processing units or processors in acomputer, cause the computer to perform operations to execute elementsinvolving the various aspects of the disclosure.

Moreover, while embodiments have been described in the context of fullyfunctioning computers and computer systems, those skilled in the artwill appreciate that the various embodiments are capable of beingdistributed as a program product in a variety of forms, and that thedisclosure applies equally regardless of the particular type of machineor computer-readable media used to actually effect the distribution.

Further examples of machine-readable storage media, machine-readablemedia, or computer-readable (storage) media include but are not limitedto recordable type media such as volatile and non-volatile memorydevices, floppy and other removable disks, hard disk drives, opticaldisks (e.g., Compact Disk Read-Only Memory (CD ROMS), Digital VersatileDisks, (DVDs), etc.), among others, and transmission type media such asdigital and analog communication links.

In some circumstances, operation of a memory device, such as a change instate from a binary one to a binary zero or vice-versa, for example, maycomprise a transformation, such as a physical transformation. Withparticular types of memory devices, such a physical transformation maycomprise a physical transformation of an article to a different state orthing. For example, but without limitation, for some types of memorydevices, a change in state may involve an accumulation and storage ofcharge or a release of stored charge. Likewise, in other memory devices,a change of state may comprise a physical change or transformation inmagnetic orientation or a physical change or transformation in molecularstructure, such as from crystalline to amorphous or vice versa. Theforegoing is not intended to be an exhaustive list in which a change instate for a binary one to a binary zero or vice-versa in a memory devicemay comprise a transformation, such as a physical transformation.Rather, the foregoing is intended as illustrative examples.

A storage medium typically may be non-transitory or comprise anon-transitory device. In this context, a non-transitory storage mediummay include a device that is tangible, meaning that the device has aconcrete physical form, although the device may change its physicalstate. Thus, for example, non-transitory refers to a device remainingtangible despite this change in state.

Remarks

The language used in the specification has been principally selected forreadability and instructional purposes, and it may not have beenselected to delineate or circumscribe the inventive subject matter. Itis, therefore, intended that the scope of the invention be limited notby this Detailed Description, but rather by any claims that issue on anapplication based hereon. Accordingly, the disclosure of variousembodiments is intended to be illustrative, but not limiting, of thescope of the embodiments, which is set forth in the following claims.

1. A computer implemented method comprising: creating a block chaincomprising a plurality of blocks by: creating a block defining anauthority of a user, the block comprising a cryptographic user IDidentifying the user and the authority associated with the cryptographicuser ID, the authority defining at least an operation associated withthe cryptographic user ID to perform on the block chain; appending theblock to an end of the block chain, wherein the block chain is notencrypted; receiving a request from a requesting device to access theblock chain, the request comprising a cryptographic user ID associatedwith the user making the request; determining whether the user makingthe request has an authority to access the block chain by computing theauthority recorded in the block chain; generating a token grantingaccess to the block chain to the user making the request upondetermining that the user making the request has the authority to accessthe block chain; and sending the token to the requesting device.
 2. Themethod of claim 1, said generating the token comprising: creating a keyidentifier identifying a secret root key; creating a permission to theblock chain granted by the token; creating a cryptographic hash of thesecret root key and the permission; and adding the key identifier, thepermission and the cryptographic hash to the token.
 3. The method ofclaim 1, said determining whether the user making the request has theauthority comprising: determining whether the user making the requesthas the authority to access the block chain by determining whether therequest is signed with a recovery key, without computing the authorityrecorded in the block chain, including checking the block chain from aninitial block to a last block; and generating a second token grantingunlimited access to the block chain to the user making the request upondetermining that the request is signed with the recovery key.
 4. Themethod of claim 3, comprising: separating the recovery key into aplurality of parts; encrypting at least a subset of parts in theplurality of parts; and distributing the encrypted subset of parts and aremainder of the plurality of parts to a plurality of devices.
 5. Themethod of claim 1, comprising: storing a first cryptographic key on aserver; sending a second cryptographic key to a user device; receiving arequest for the first cryptographic key from the user device;determining whether the user device is permitted to receive the firstcryptographic key upon receiving the request; and refusing to send thefirst cryptographic key upon determining that the user device is notpermitted to receive the first cryptographic key.
 6. The method of claim1, comprising: receiving an update regarding an interpretation ofsemantics of the block chain; and ensuring consistency of theinterpretation of semantics of the block chain across a plurality ofuser devices by storing the update within the block chain.
 7. A systemcomprising: one or more processors; and memory coupled to the one ormore processors, wherein the memory includes instructions executable bythe one or more processors to: create a block chain comprising aplurality of blocks by: creating a block defining an authority of auser, the block comprising a user ID identifying the user and theauthority associated with the user ID, the authority defining at leastan operation associated with the user ID to perform on the block chain;appending the block to an end of the block chain, wherein the blockchain is not encrypted; receive a request from a requesting device toaccess the block chain, the request comprising a user ID associated withthe user making the request; determine whether the user making therequest has an authority to access the block chain by computing theauthority recorded in the block chain; generate a token granting accessto the block chain to the user making the request upon determining thatthe user making the request has the authority to access the block chain;and send the token to the requesting device.
 8. The system of claim 7,comprising the instructions to: obtain at least two authority sourcescontrolling access to an encrypted data, a first authority source amongthe at least two authority sources including the block chain defining afirst access associated with the user to the encrypted data, a secondauthority source among the at least two authority sources defining asecond access associated with the user to the encrypted data granted tothe user by a third-party; determine whether the first authority sourcegrants the requested access and whether the second authority sourcegrants the requested access; and generate the token upon determiningthat the first authority source and the second authority source grantthe requested access.
 9. The system of claim 7, the instructions togenerate the token comprising the instructions to: create a keyidentifier identifying a secret root key; create a permission to theblock chain granted by the token; create a cryptographic hash of thesecret root key and the permission; and add the key identifier, thepermission and the cryptographic hash to the token.
 10. The system ofclaim 7, the instructions to determine whether the user making therequest has the authority comprising the instructions to: determinewhether the user making the request has the authority to access theblock chain by determining whether the request is signed with a recoverykey, without computing the authority recorded in the block chain,including checking the block chain from an initial block to a lastblock; and generate a second token granting unlimited access to theblock chain to the user making the request upon determining that therequest is signed with the recovery key.
 11. The system of claim 10,comprising the instructions to: separate the recovery key into aplurality of parts; encrypt at least a subset of parts in the pluralityof parts; and distribute the encrypted subset of parts and a remainderof the plurality of parts to a plurality of devices.
 12. The system ofclaim 7, comprising the instructions to: store a first cryptographic keyon a server; send a second cryptographic key to a user device; receive arequest for the first cryptographic key from the user device; determinewhether the user device is permitted to receive the first cryptographickey upon receiving the request; and refuse to send the firstcryptographic key upon determining that the user device is not permittedto receive the first cryptographic key.
 13. The system of claim 7,comprising the instructions to: receive an update regarding aninterpretation of semantics of the block chain; and ensure consistencyof the interpretation of semantics of the block chain across a pluralityof user devices by storing the update within the block chain.
 14. Atleast one computer-readable medium, excluding transitory signals andcarrying instructions that, when executed by at least one dataprocessor, performs a method comprising: creating a block chaincomprising a plurality of blocks by: creating a block defining anauthority of a user, the block comprising a user ID identifying the userand the authority associated with the user ID, the authority defining atleast an operation associated with the user ID to perform on the blockchain; appending the block to an end of the block chain, wherein theblock chain is not encrypted; receiving a request from a requestingdevice to access the block chain, the request comprising a user IDassociated with the user making the request; determining whether theuser making the request has an authority to access the block chain bycomputing the authority recorded in the block chain; generating a tokengranting access to the block chain to the user making the request upondetermining that the user making the request has the authority to accessthe block chain; and sending the token to the requesting device.
 15. Thecomputer readable medium of claim 14, comprising: obtaining at least twoauthority sources controlling access to an encrypted data, a firstauthority source among the at least two authority sources including theblock chain defining a first access associated with the user to theencrypted data, a second authority source among the at least twoauthority sources defining a second access associated with the user tothe encrypted data granted to the user by a third-party; determiningwhether the first authority source grants the requested access andwhether the second authority source grants the requested access; andgenerating the token upon determining that the first authority sourceand the second authority source grant the requested access.
 16. Thecomputer readable medium of claim 14, said generating the tokencomprising: creating a key identifier identifying a secret root key;creating a permission to the block chain granted by the token; creatinga cryptographic hash of the secret root key and the permission; andadding the key identifier, the permission and the cryptographic hash tothe token.
 17. The computer readable medium of claim 14, saiddetermining whether the user making the request has the authoritycomprising: determining whether the user making the request has theauthority to access the block chain by determining whether the requestis signed with a recovery key, without computing the authority recordedin the block chain, including checking the block chain from an initialblock to a last block; and generating a second token granting unlimitedaccess to the block chain to the user making the request upondetermining that the request is signed with the recovery key.
 18. Thecomputer readable medium of claim 17, comprising: separating therecovery key into a plurality of parts; encrypting at least a subset ofparts in the plurality of parts; and distributing the encrypted subsetof parts and a remainder of the plurality of parts to a plurality ofdevices.
 19. The computer readable medium of claim 14, comprising:storing a first cryptographic key on a server; sending a secondcryptographic key to a user device; receiving a request for the firstcryptographic key from the user device; determining whether the userdevice is permitted to receive the first cryptographic key uponreceiving the request; and refusing to send the first cryptographic keyupon determining that the user device is not permitted to receive thefirst cryptographic key.
 20. The computer readable medium of claim 14,comprising: receiving an update regarding an interpretation of semanticsof the block chain; and ensuring consistency of the interpretation ofsemantics of the block chain across a plurality of user devices bystoring the update within the block chain.